linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Support "-t nfs,vers=4" mounts in the kernel [take 4]
Date: Wed, 09 Sep 2009 14:14:43 -0400	[thread overview]
Message-ID: <4AA7F093.4030902@RedHat.com> (raw)
In-Reply-To: <1252517471.8722.19.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>



On 09/09/2009 01:31 PM, Trond Myklebust wrote:
> On Tue, 2009-09-08 at 14:51 -0400, Steve Dickson wrote:
>> On 09/02/2009 09:51 AM, Chuck Lever wrote:
>>> Sorry for the repost.  After reading the patch descriptions again, I
>>> thought they needed some clarification.
>>>
>>> ---
>>>
>>> Chuck Lever (4):
>>>       NFS: Allow the "nfs" file system type to support NFSv4
>>>       NFS: Move details of nfs4_get_sb() to a helper
>>>       NFS: Refactor NFSv4 text-based mount option validation
>>>       NFS: Mount option parser should detect missing "port="
>>>
>>>
>>>  fs/nfs/internal.h    |   10 ++
>>>  fs/nfs/super.c       |  202 +++++++++++++++++++++++++++++++++-----------------
>>>  include/linux/nfs4.h |    1 
>>>  3 files changed, 144 insertions(+), 69 deletions(-)
>>>
>> Trond,
>>
>> I'm updating the mount.nfs man pages, and would like give 
>> an guess-ta-mate as to which kernel these patches will be in.
>> Any ideas?
> 
> I'm planning on pushing them out in the upcoming merge window, since the
> patches themselves seem pretty straightforward. I've applied the fixes
> that I suggested, and added the patch to disable vers!=4 in the '-t
> nfs4' case.
> 
> If you'd like to test it all out, I've pushed those patches into the
> nfs-for-2.6.32 branch of my git tree. They should also appear in
> linux-next.
Cool... thanks!

steved.

  parent reply	other threads:[~2009-09-09 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 13:51 [PATCH 0/4] Support "-t nfs,vers=4" mounts in the kernel [take 4] Chuck Lever
     [not found] ` <20090902135032.3550.23170.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-09-02 13:52   ` [PATCH 1/4] NFS: Mount option parser should detect missing "port=" Chuck Lever
2009-09-02 13:52   ` [PATCH 2/4] NFS: Refactor NFSv4 text-based mount option validation Chuck Lever
2009-09-02 13:52   ` [PATCH 3/4] NFS: Move details of nfs4_get_sb() to a helper Chuck Lever
2009-09-02 13:52   ` [PATCH 4/4] NFS: Allow the "nfs" file system type to support NFSv4 Chuck Lever
     [not found]     ` <20090902135222.3550.59986.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-09-08 22:17       ` Trond Myklebust
2009-09-02 15:10   ` [PATCH 0/4] Support "-t nfs,vers=4" mounts in the kernel [take 4] Steve Dickson
2009-09-08 18:51   ` Steve Dickson
     [not found]     ` <4AA6A7B5.1060301-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-09-09 17:31       ` Trond Myklebust
     [not found]         ` <1252517471.8722.19.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-09-09 18:14           ` Steve Dickson [this message]
2009-09-14 18:17           ` Steve Dickson
     [not found]             ` <4AAE88B8.90908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-09-14 18:28               ` 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=4AA7F093.4030902@RedHat.com \
    --to=steved@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).