From: Jani Nikula <jani.nikula@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>, Jonathan Corbet <corbet@lwn.net>
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: Mon, 01 Dec 2025 19:35:46 +0200 [thread overview]
Message-ID: <b2ff1286390fd48b1f62638980a2082e785de913@intel.com> (raw)
In-Reply-To: <20251119190955.GGaR4WAyMn7tkLhgeN@fat_crate.local>
On Wed, 19 Nov 2025, Borislav Petkov <bp@alien8.de> wrote:
> On Wed, Nov 19, 2025 at 08:42:43AM -0700, Jonathan Corbet wrote:
>> 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.
>
> That would've been my next idea...
That's how it was originally, but that lead to some problems with the
PDF builds. I wish I could tell you what the issues were specifically,
instead I just have to blame my past self for not recording the details
in the commit message properly: e52347bd66f6
("Documentation/admin-guide: split the kernel parameter list to a
separate file").
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-12-01 17:35 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
2025-11-19 19:09 ` Borislav Petkov
2025-12-01 17:35 ` Jani Nikula [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=b2ff1286390fd48b1f62638980a2082e785de913@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=corbet@lwn.net \
--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).