From: Chuck Lever III <chuck.lever@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
coverity-bot <keescook@chromium.org>,
"yzaikin@google.com" <yzaikin@google.com>,
"j.granados@samsung.com" <j.granados@samsung.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] sunrpc: simplify two-level sysctl registration for tsvcrdma_parm_table
Date: Sun, 12 Mar 2023 01:22:40 +0000 [thread overview]
Message-ID: <CFC1180E-DA7B-45AA-8FE5-77A9A397BBFD@oracle.com> (raw)
In-Reply-To: <ZA0nvzJuWYPNLR/c@bombadil.infradead.org>
> On Mar 11, 2023, at 8:15 PM, Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> On Sun, Mar 12, 2023 at 01:06:26AM +0000, Chuck Lever III wrote:
>>
>>
>>> On Mar 11, 2023, at 6:39 PM, Luis Chamberlain <mcgrof@kernel.org> wrote:
>>>
>>> There is no need to declare two tables to just create directories,
>>> this can be easily be done with a prefix path with register_sysctl().
>>>
>>> Simplify this registration.
>>>
>>> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
>>
>> I can take this one, but I'm wondering what "tsvcrdma_parm_table"
>> is (see the short description).
>
> Heh sorry tsvcrdma_parm_table was
> supposed to be svcrdma_parm_table.
>
> Sorry for the typo.
>
> Can you fix or wuold you like me to resend?
I'll fix it up, just wanted confirmation that I wasn't missing
something important!
--
Chuck Lever
next prev parent reply other threads:[~2023-03-12 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 23:39 [PATCH v3 0/5] sunrpc: simplfy sysctl registrations Luis Chamberlain
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 [this message]
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=CFC1180E-DA7B-45AA-8FE5-77A9A397BBFD@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--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=mcgrof@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).