From: Andi Kleen <ak@suse.de>
To: Bruce Allan <bruce.allan@us.ibm.com>
Cc: trond.myklebust@fys.uio.no, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Support non reserved ports for NFS client
Date: Wed, 18 Jun 2003 22:57:19 +0200 [thread overview]
Message-ID: <20030618205719.GA3543@wotan.suse.de> (raw)
In-Reply-To: <OF90A826B7.444525BC-ON88256D49.006D66FE-88256D49.006E8344@us.ibm.com>
On Wed, Jun 18, 2003 at 01:07:05PM -0700, Bruce Allan wrote:
> May I make the suggestion that instead of creating a new flag (i.e.
> NFS_MOUNT_NONRESERVED) and using a new bit in the flags field of struct
> nfs_mount_data, Andi use the already existing and unused NFS_MOUNT_SECURE
> assuming that is what was originally intended for this bit. This would
> also match in name with the secure/insecure export option on the server.
Makes sense yes. Thanks for the suggestion.
-Andi
next prev parent reply other threads:[~2003-06-18 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 20:07 Bruce Allan
2003-06-18 20:57 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 14:51 Andi Kleen
2003-06-18 18:32 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030618205719.GA3543@wotan.suse.de \
--to=ak@suse.de \
--cc=bruce.allan@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®