From: Jonathan Corbet <corbet@lwn.net>
To: Borislav Petkov <bp@kernel.org>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH] Documentation/kernel-parameters: Move the kernel build options
Date: Tue, 18 Nov 2025 09:20:36 -0700 [thread overview]
Message-ID: <87a50j5n3f.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251112114641.8230-1-bp@kernel.org>
Borislav Petkov <bp@kernel.org> writes:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
>
> Move the kernel build options abbreviations to the .txt file so that
> they are together instead of one having to go hunt them in the .rst
> file.
>
> Tweak the formatting so that the inclusion of kernel-parameters.txt
> still keeps the whole thing somewhat presentable in the html output too.
>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
> .../admin-guide/kernel-parameters.rst | 97 +-----------------
> .../admin-guide/kernel-parameters.txt | 98 +++++++++++++++++++
> 2 files changed, 99 insertions(+), 96 deletions(-)
So I applied this, but it's dancing around the real problem: that this
material is split into two files in the first place. I honestly don't
remember why it was done that way - maybe just to ease the RST
transition back in 2016. I think we should really just pull all of
kernel-parameters.txt into the RST file.
jon
next prev parent reply other threads:[~2025-11-18 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 11:46 [PATCH] Documentation/kernel-parameters: Move the kernel build options Borislav Petkov
2025-11-13 1:12 ` Randy Dunlap
2025-11-18 16:20 ` Jonathan Corbet [this message]
2025-11-19 15:06 ` Borislav Petkov
2025-11-19 15:42 ` Jonathan Corbet
2025-11-19 19:09 ` Borislav Petkov
2025-12-01 17:35 ` Jani Nikula
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=87a50j5n3f.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.