public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Documentation: kernel-parameters: sort NFS parameters
Date: Tue, 14 Mar 2023 12:46:59 -0600	[thread overview]
Message-ID: <871qlrrx0c.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230227025816.1083-1-rdunlap@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> Sort the NFS kernel command line parameters. This is done in 4 groups
> so as to not have them intermingled: 'nfs' module parameters, 'nfs4'
> module parameters, 'nfsd' module parameters, and nfs "global" (__setup,
> no module) parameters.
>
> There were 5 parameters which were listed with a space between the
> parameter name and the following '=' sign. The space has been
> removed since module parameters expect 'parameter=' with no intervening
> space.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Trond Myklebust <trond.myklebust@hammerspace.com>
> Cc: Anna Schumaker <anna@kernel.org>
> Cc: Chuck Lever <chuck.lever@oracle.com>
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: linux-nfs@vger.kernel.org
> ---
>  Documentation/admin-guide/kernel-parameters.txt |   74 +++++++-------
>  1 file changed, 37 insertions(+), 37 deletions(-)

Applied,

thanks.

jon

      reply	other threads:[~2023-03-14 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  2:58 [PATCH] Documentation: kernel-parameters: sort NFS parameters Randy Dunlap
2023-03-14 18:46 ` Jonathan Corbet [this message]

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=871qlrrx0c.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=trond.myklebust@hammerspace.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