From: Mike Rapoport <rppt@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] docs: kernel-parameters: adjust reserve_mem build option
Date: Sun, 4 Oct 2026 21:35:49 +0200 [thread overview]
Message-ID: <asKqlZFS_A42w2hb@kernel.org> (raw)
In-Reply-To: <20261003213457.96408-1-rdunlap@infradead.org>
On Sat, Oct 03, 2026 at 02:34:57PM -0700, Randy Dunlap wrote:
> "[RAM]" means that the command line option is applicable when
> "RAM disk support is enabled." However, the reserve_mem command line
> option is not related to RAM disk support, so modify its build option
> relevance to "[MM]" instead.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: linux-doc@vger.kernel.org
> Cc: Mike Rapoport <rppt@kernel.org>
> Cc: linux-mm@kvack.org
>
> Documentation/admin-guide/kernel-parameters.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20261002.orig/Documentation/admin-guide/kernel-parameters.txt
> +++ linux-next-20261002/Documentation/admin-guide/kernel-parameters.txt
> @@ -6693,7 +6693,7 @@ Kernel parameters
> them. If <base> is less than 0x10000, the region
> is assumed to be I/O ports; otherwise it is memory.
>
> - reserve_mem= [RAM]
> + reserve_mem= [MM]
> Format: nn[KMG]:<align>:<label>
> Reserve physical memory and label it with a name that
> other subsystems can use to access it. This is typically
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-10-04 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 21:34 [PATCH] docs: kernel-parameters: adjust reserve_mem build option Randy Dunlap
2026-10-04 19:35 ` Mike Rapoport [this message]
2026-10-08 11:30 ` SJ Park
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=asKqlZFS_A42w2hb@kernel.org \
--to=rppt@kernel.org \
--cc=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 \
/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