From: Bryan Schumaker <bjschuma@netapp.com>
To: Jim Rees <rees@umich.edu>
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/7] NFS: Rename nfs4_proc_get_root()
Date: Mon, 30 Apr 2012 15:10:45 -0400 [thread overview]
Message-ID: <4F9EE3B5.4060502@netapp.com> (raw)
In-Reply-To: <20120430190743.GA2461@umich.edu>
On 04/30/2012 03:07 PM, Jim Rees wrote:
> bjschuma@netapp.com wrote:
>
> From: Bryan Schumaker <bjschuma@netapp.com>
>
> This function is really getting the root filehandle and not the root
> dentry of the filesystem. I also removed the rpc_ops lookup from
> nfs4_get_rootfh() under the assumption that if we reach this function
> then we already know we are using NFS v4.
>
> And when NFSv5 comes out?
Well, this function is called "nfs4_get_rootfh()". nfs5_get_rootfh() will probably be something different and also not need an rpc op...
- Bryan
next prev parent reply other threads:[~2012-04-30 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:40 [PATCH 0/7] Clean up mount functions bjschuma
2012-04-30 18:40 ` [PATCH 1/7] NFS: Rename nfs4_proc_get_root() bjschuma
2012-04-30 19:07 ` Jim Rees
2012-04-30 19:10 ` Bryan Schumaker [this message]
2012-04-30 19:38 ` Myklebust, Trond
2012-04-30 18:40 ` [PATCH 2/7] NFS: Create a single nfs_get_root() bjschuma
2012-04-30 18:40 ` [PATCH 3/7] NFS: Consistent arguments to nfs_fscache_get_super_cookie() bjschuma
2012-05-07 17:46 ` Myklebust, Trond
2012-04-30 18:40 ` [PATCH 4/7] NFS: Create a common fs_mount() function bjschuma
2012-04-30 18:40 ` [PATCH 5/7] NFS: Create a common xdev_mount() function bjschuma
2012-05-07 18:11 ` Myklebust, Trond
2012-04-30 18:40 ` [PATCH 6/7] NFS: Use nfs_fs_mount_common() for xdev mounts bjschuma
2012-05-01 18:21 ` Bryan Schumaker
2012-04-30 18:40 ` [PATCH 7/7] NFS: Use nfs_fs_mount_common() for remote referral mounts bjschuma
2012-05-07 18:10 ` Myklebust, Trond
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=4F9EE3B5.4060502@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.