From: Chuck Lever <chuck.lever@oracle.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Three tiny clean-ups for 3.2 (repost)
Date: Tue, 25 Oct 2011 12:17:32 -0400 [thread overview]
Message-ID: <20111025161631.5996.30680.stgit@seurat.1015granger.net> (raw)
I found these nits on the wayward journey to implementing client-side
migration support.
---
Chuck Lever (3):
NFS: Remove no-op less-than-zero checks on unsigned variables.
NFS: Clean up nfs4_xdr_dec_secinfo()
NFS: Fix documenting comment for nfs_create_request()
fs/nfs/nfs4filelayout.c | 7 +++----
fs/nfs/nfs4xdr.c | 2 --
fs/nfs/pagelist.c | 2 +-
3 files changed, 4 insertions(+), 7 deletions(-)
--
Chuck Lever
next reply other threads:[~2011-10-25 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 16:17 Chuck Lever [this message]
2011-10-25 16:17 ` [PATCH 1/3] NFS: Fix documenting comment for nfs_create_request() Chuck Lever
2011-10-25 16:17 ` [PATCH 2/3] NFS: Clean up nfs4_xdr_dec_secinfo() Chuck Lever
2011-10-27 10:51 ` Bryan Schumaker
2011-10-25 16:18 ` [PATCH 3/3] NFS: Remove no-op less-than-zero checks on unsigned variables Chuck Lever
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=20111025161631.5996.30680.stgit@seurat.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=Trond.Myklebust@netapp.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).