From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/6] Replace NFSROOT mount option parsing
Date: Fri, 10 Sep 2010 16:03:09 -0400 [thread overview]
Message-ID: <20100910200001.13167.61153.stgit@seurat.1015granger.net> (raw)
Trond-
For 2.6.37, it would be nice to eliminate the redundant mount option
parsing logic in fs/nfs/nfsroot.c. Merged up to 2.6.36-rc, and
compile-tested.
We had discussed, as a first step, merging these into linux-next.
I unit-tested these on late 2.6.34-rc kernels, so there might be an
additional detail or two to clean up.
---
Chuck Lever (6):
SUNRPC: Remove rpcb_getport_sync()
NFS: Allow NFSROOT debugging messages to be enabled dynamically
NFS: Clean up nfsroot.c
NFS: Use super.c for NFSROOT mount option parsing
NFS: Clean up NFSROOT command line parsing
NFS: Remove \t from mount debugging message
Documentation/filesystems/nfs/nfsroot.txt | 22 +
Documentation/kernel-parameters.txt | 5
fs/nfs/mount_clnt.c | 2
fs/nfs/nfsroot.c | 566 +++++++++--------------------
include/linux/nfs_fs.h | 10 -
include/linux/sunrpc/clnt.h | 1
init/do_mounts.c | 12 -
net/sunrpc/rpcb_clnt.c | 51 ---
8 files changed, 208 insertions(+), 461 deletions(-)
--
Chuck Lever
next reply other threads:[~2010-09-10 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 20:03 Chuck Lever [this message]
2010-09-10 20:03 ` [PATCH 1/6] NFS: Remove \t from mount debugging message Chuck Lever
2010-09-10 20:03 ` [PATCH 2/6] NFS: Clean up NFSROOT command line parsing Chuck Lever
2010-09-10 20:03 ` [PATCH 3/6] NFS: Use super.c for NFSROOT mount option parsing Chuck Lever
2010-09-10 20:03 ` [PATCH 4/6] NFS: Clean up nfsroot.c Chuck Lever
2010-09-10 20:04 ` [PATCH 5/6] NFS: Allow NFSROOT debugging messages to be enabled dynamically Chuck Lever
2010-09-10 20:04 ` [PATCH 6/6] SUNRPC: Remove rpcb_getport_sync() Chuck Lever
2010-09-17 21:44 ` [PATCH 0/6] Replace NFSROOT mount option parsing 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=20100910200001.13167.61153.stgit@seurat.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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).