From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: Re: [PATCH] docs: kernel-parameters: don't mix cmdline options & build options
Date: Wed, 14 Oct 2026 11:04:53 -0600 [thread overview]
Message-ID: <87bj8ww6ve.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261003213508.96424-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> Some kernel command line descriptions mix, mingle, or conflate an
> optional part of the command line with the build options that are
> applicable to those command line options.
>
> Specifically, a few command line options that use "KMG" to specify
> a memory size mix that string with build options like "X86,EARLY".
> These should be separate fields although they are both enclosed in
> square brackets, so separate the conflated fields.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: x86@kernel.org
>
> Documentation/admin-guide/kernel-parameters.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- linux-next-20260930.orig/Documentation/admin-guide/kernel-parameters.txt
> +++ linux-next-20260930/Documentation/admin-guide/kernel-parameters.txt
> @@ -4080,8 +4080,8 @@ Kernel parameters
> like Grub2, otherwise '$' and the following number
> will be eaten.
>
> - memmap=nn[KMG]!ss[KMG,EARLY]
> - [KNL,X86] Mark specific memory as protected.
> + memmap=nn[KMG]!ss[KMG]
> + [KNL,X86,EARLY] Mark specific memory as protected.
> Region of memory to be used, from ss to ss+nn.
> The memory region may be marked as e820 type 12 (0xc)
> and is NVDIMM or ADR memory.
> @@ -4371,11 +4371,11 @@ Kernel parameters
> Enable printing debug information related to MTRR
> registers at boot time.
>
> - mtrr_chunk_size=nn[KMG,X86,EARLY]
> + mtrr_chunk_size=nn[KMG] [X86,EARLY]
> used for mtrr cleanup. It is largest continuous chunk
> that could hold holes aka. UC entries.
>
> - mtrr_gran_size=nn[KMG,X86,EARLY]
> + mtrr_gran_size=nn[KMG] [X86,EARLY]
> Used for mtrr cleanup. It is granularity of mtrr block.
Applied, thanks.
jon
prev parent reply other threads:[~2026-10-14 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 21:35 [PATCH] docs: kernel-parameters: don't mix cmdline options & build options Randy Dunlap
2026-10-14 17:04 ` 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=87bj8ww6ve.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=x86@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