linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: chuck.lever@oracle.com, jlayton@kernel.org,
	trond.myklebust@hammerspace.com, anna@kernel.org,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	kuba@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, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH v3 0/5] sunrpc: simplfy sysctl registrations
Date: Sat, 11 Mar 2023 15:39:39 -0800	[thread overview]
Message-ID: <20230311233944.354858-1-mcgrof@kernel.org> (raw)

This is my v3 series to simplify sysctl registration for sunrpc. The
first series was posted just yesterday [0] but 0-day found an issue with
CONFIG_SUNRPC_DEBUG. After this fix I poasted a fix for v2 [1] but alas
0-day then found an issue when CONFIG_SUNRPC_DEBUG is disabled. This
fixes both cases... hopefully that's it.
                                                                                                                                                                                              
Changes on v3:

   o Fix compilation when CONFIG_SUNRPC_DEBUG is disabled.. forgot to
     keep all the sysctl stuff under the #ifdef.

Changes on v2:

   o Fix compilation when CONFIG_SUNRPC_DEBUG is enabled, I forgot to move the
     proc routines above, and so the 4th patch now does that too.
                                                                                                                                                                                              
Feel free to take these patches or let me know and I'm happy to also
take these in through sysctl-next. Typically I use sysctl-next for
core sysctl changes or for kernel/sysctl.c cleanup to avoid conflicts.
All these syctls however are well contained to sunrpc so they can also
go in separately. Let me know how you'd like to go about these patches.
                                                                                                                                                                                              
[0] https://lkml.kernel.org/r/20230310225236.3939443-1-mcgrof@kernel.org

Luis Chamberlain (5):
  sunrpc: simplify two-level sysctl registration for tsvcrdma_parm_table
  sunrpc: simplify one-level sysctl registration for xr_tunables_table
  sunrpc: simplify one-level sysctl registration for xs_tunables_table
  sunrpc: move sunrpc_table and proc routines above
  sunrpc: simplify one-level sysctl registration for debug_table

 net/sunrpc/sysctl.c             | 42 ++++++++++++---------------------
 net/sunrpc/xprtrdma/svc_rdma.c  | 21 ++---------------
 net/sunrpc/xprtrdma/transport.c | 11 +--------
 net/sunrpc/xprtsock.c           | 13 ++--------
 4 files changed, 20 insertions(+), 67 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-03-11 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 23:39 Luis Chamberlain [this message]
2023-03-11 23:39 ` [PATCH v3 1/5] sunrpc: simplify two-level sysctl registration for tsvcrdma_parm_table Luis Chamberlain
2023-03-12  1:06   ` Chuck Lever III
2023-03-12  1:15     ` Luis Chamberlain
2023-03-12  1:22       ` Chuck Lever III
2023-03-11 23:39 ` [PATCH v3 2/5] sunrpc: simplify one-level sysctl registration for xr_tunables_table Luis Chamberlain
2023-03-11 23:39 ` [PATCH v3 3/5] sunrpc: simplify one-level sysctl registration for xs_tunables_table Luis Chamberlain
2023-03-11 23:39 ` [PATCH v3 4/5] sunrpc: move sunrpc_table and proc routines above Luis Chamberlain
2023-03-11 23:39 ` [PATCH v3 5/5] sunrpc: simplify one-level sysctl registration for debug_table Luis Chamberlain
2023-03-13 10:48 ` [PATCH v3 0/5] sunrpc: simplfy sysctl registrations 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=20230311233944.354858-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=edumazet@google.com \
    --cc=j.granados@samsung.com \
    --cc=jlayton@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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).