From: Luis Chamberlain <mcgrof@kernel.org>
To: chuck.lever@oracle.com, jlayton@kernel.org,
trond.myklebust@hammerspace.com, anna@kernel.org,
linux-nfs@vger.kernel.org
Cc: ebiederm@xmission.com, keescook@chromium.org, yzaikin@google.com,
j.granados@samsung.com, patches@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>
Subject: nfs/lockd: simplify sysctl registration
Date: Fri, 10 Mar 2023 14:58:39 -0800 [thread overview]
Message-ID: <20230310225842.3946871-1-mcgrof@kernel.org> (raw)
This is just following the work of the same sysctl registration [0] I
just emailed you patches for sunprc but for nfs and lockd.
Feel free to pick up or let me know if you want me to take them through
my tree. I haven't even finished compile testing all these yet, but they
are pretty trivial.
I'm just dropping netdev on this series as its purely nfs/lockd stuff.
[0] https://lkml.kernel.org/r/20230310225236.3939443-1-mcgrof@kernel.org
Luis Chamberlain (3):
lockd: simplify two-level sysctl registration for nlm_sysctls
nfs: simplify two-level sysctl registration for nfs4_cb_sysctls
nfs: simplify two-level sysctl registration for nfs_cb_sysctls
fs/lockd/svc.c | 20 +-------------------
fs/nfs/nfs4sysctl.c | 21 ++-------------------
fs/nfs/sysctl.c | 20 +-------------------
3 files changed, 4 insertions(+), 57 deletions(-)
--
2.39.1
next reply other threads:[~2023-03-10 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 22:58 Luis Chamberlain [this message]
2023-03-10 22:58 ` [PATCH 1/3] lockd: simplify two-level sysctl registration for nlm_sysctls Luis Chamberlain
2023-03-10 22:58 ` [PATCH 2/3] nfs: simplify two-level sysctl registration for nfs4_cb_sysctls Luis Chamberlain
2023-03-10 22:58 ` [PATCH 3/3] nfs: simplify two-level sysctl registration for nfs_cb_sysctls Luis Chamberlain
2023-03-13 10:49 ` nfs/lockd: simplify sysctl registration Jeff Layton
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=20230310225842.3946871-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=ebiederm@xmission.com \
--cc=j.granados@samsung.com \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=trond.myklebust@hammerspace.com \
--cc=yzaikin@google.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).