From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: <Trond.Myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] Remove function macros from nfs4_fs.h
Date: Mon, 5 Jan 2015 14:17:21 -0500 [thread overview]
Message-ID: <1420485444-20101-1-git-send-email-Anna.Schumaker@Netapp.com> (raw)
While reviewing Tom's flexfile patches I found a few places where
nfs4_state_protect() was being called inside the generic client, rather
than in the nfsv4 module. These patches move the function calls into
the correct layer and then tidy up nfs4_fs.h once everything has been
moved.
Thoughts?
Anna
Anna Schumaker (3):
nfs: Call nfs4_state_protect() from nfs4_proc_commit_setup()
nfs: Call nfs4_state_protect_write() from nfs4_proc_write_setup()
nfs: Remove unused v4 macros
fs/nfs/nfs3proc.c | 7 +++++--
fs/nfs/nfs4_fs.h | 7 -------
fs/nfs/nfs4proc.c | 9 +++++++--
fs/nfs/proc.c | 6 ++++--
fs/nfs/write.c | 10 ++--------
include/linux/nfs_xdr.h | 6 ++++--
6 files changed, 22 insertions(+), 23 deletions(-)
--
2.2.1
next reply other threads:[~2015-01-05 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 19:17 Anna Schumaker [this message]
2015-01-05 19:17 ` [PATCH 1/3] nfs: Call nfs4_state_protect() from nfs4_proc_commit_setup() Anna Schumaker
2015-01-05 19:17 ` [PATCH 2/3] nfs: Call nfs4_state_protect_write() from nfs4_proc_write_setup() Anna Schumaker
2015-01-05 19:17 ` [PATCH 3/3] nfs: Remove unused v4 macros Anna Schumaker
2015-01-05 20:31 ` [PATCH 0/3] Remove function macros from nfs4_fs.h Weston Andros Adamson
2015-01-05 21:06 ` Anna Schumaker
2015-01-05 21:51 ` Weston Andros Adamson
2015-01-06 15:02 ` Weston Andros Adamson
2015-01-06 19:08 ` J. Bruce Fields
2015-01-07 18:47 ` Weston Andros Adamson
2015-01-07 18:55 ` J. Bruce Fields
2015-01-07 18:57 ` J. Bruce Fields
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=1420485444-20101-1-git-send-email-Anna.Schumaker@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=Trond.Myklebust@primarydata.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