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
Subject: Re: [PATCH] Documentation: admin: move OOO entries in kernel-parameters.txt
Date: Mon, 02 Jan 2023 16:19:05 -0700 [thread overview]
Message-ID: <87zgb0h6dy.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221204013050.11496-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Fix the most blatant out-of-order entries in kernel-parameters.txt.
>
> No changes other than modifying the order of the entries.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
> Do not backport.
>
> Documentation/admin-guide/kernel-parameters.txt | 122 +++++++-------
> 1 file changed, 61 insertions(+), 61 deletions(-)
Applied - better late than never...
Thanks,
jon
prev parent reply other threads:[~2023-01-02 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 1:30 [PATCH] Documentation: admin: move OOO entries in kernel-parameters.txt Randy Dunlap
2022-12-04 4:10 ` Bagas Sanjaya
2022-12-04 5:23 ` Randy Dunlap
2023-01-02 23:19 ` 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=87zgb0h6dy.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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