From: Jonathan Corbet <corbet@lwn.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Borislav Petkov <bp@kernel.org>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/kernel-parameters: Move the kernel build options
Date: Wed, 19 Nov 2025 08:42:43 -0700 [thread overview]
Message-ID: <87ldk2111o.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251119150616.GDaR3c6MW9VkFKpH_C@fat_crate.local>
Borislav Petkov <bp@alien8.de> writes:
> On Tue, Nov 18, 2025 at 09:20:36AM -0700, Jonathan Corbet wrote:
>> 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
>
> I was wondering the same thing.
>
>> - 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.
>
> Except the .txt file has its own formatting and if the conversion to .rst
> makes it more unreadable due to the .rst formatting gunk, that would be a step
> in the wrong direction, I'd say.
>
> So including it verbatim as it is done now looks like a good compromise.
> Unless you have a better idea...
What the effect would be of making it all into proper RST is unclear, I
don't think anybody has tried.
But we could certainly just put the whole contents of
kernel-parameters.txt as a literal block within kernel-parameters.rst
and at least have it all in one place.
jon
next prev parent reply other threads:[~2025-11-19 15:42 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
2025-11-19 15:06 ` Borislav Petkov
2025-11-19 15:42 ` Jonathan Corbet [this message]
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=87ldk2111o.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 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).