public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: paulmck@kernel.org, Masami Hiramatsu <mhiramat@kernel.org>
Cc: mtk.manpages@gmail.com, corbet@lwn.net,
	akpm@linux-foundation.org, ndesaulniers@google.com,
	vbabka@suse.cz, hannes@cmpxchg.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] proc.5: Clarify that boot arguments can be embedded in image
Date: Sat, 8 Jul 2023 19:19:02 +0200	[thread overview]
Message-ID: <0b4048d4-e80d-a80c-d16d-3fbb301cf698@kernel.org> (raw)
In-Reply-To: <d3057de8-39ca-4d2a-aa03-9134f916fac9@paulmck-laptop>


[-- Attachment #1.1: Type: text/plain, Size: 1844 bytes --]

Hi Paul!

On 7/5/23 22:33, Paul E. McKenney wrote:
> On Tue, Jul 04, 2023 at 09:59:32PM +0900, Masami Hiramatsu wrote:
>> On Fri, 30 Jun 2023 16:33:28 -0700
>> "Paul E. McKenney" <paulmck@kernel.org> wrote:
>>
>>> With the advent of the CONFIG_BOOT_CONFIG Kconfig option, kernel boot
>>> arguments can now be embedded in the kernel image, either attached
>>> to the end of initramfs or embedded in the kernel itself.  Document
>>> this possibility in the /proc/cmdline entry of proc.5.
>>
>> Thanks for update!
>>
>> Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 

Thanks for the review!  Tag added.

> Thank you, Masami!
> 
> Adding Alejandro and linux-man on CC.
> 
> 							Thanx, Paul
> 
>>> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>>> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
>>> Cc: Masami Hiramatsu <mhiramat@kernel.org>
>>> Cc: Jonathan Corbet <corbet@lwn.net>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: Nick Desaulniers <ndesaulniers@google.com>
>>> Cc: Vlastimil Babka <vbabka@suse.cz>
>>> Cc: Johannes Weiner <hannes@cmpxchg.org>
>>>

Thanks!  Patch applied.

Cheers,
Alex

>>> diff --git a/man5/proc.5 b/man5/proc.5
>>> index c6684620e..141a2983c 100644
>>> --- a/man5/proc.5
>>> +++ b/man5/proc.5
>>> @@ -3100,6 +3100,9 @@ Often done via a boot manager such as
>>>   .BR lilo (8)
>>>   or
>>>   .BR grub (8).
>>> +Any arguments embedded in the kernel image or initramfs via
>>> +.B CONFIG_BOOT_CONFIG
>>> +will also be displayed.
>>>   .TP
>>>   .IR /proc/config.gz " (since Linux 2.6)"
>>>   This file exposes the configuration options that were used
>>
>>
>> -- 
>> Masami Hiramatsu (Google) <mhiramat@kernel.org>

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-07-08 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <433d742b-743b-4335-878f-1ca0f45698f7@paulmck-laptop>
     [not found] ` <20230704215932.c9cab0af086528e52ca0bfbb@kernel.org>
2023-07-05 20:33   ` [PATCH] proc.5: Clarify that boot arguments can be embedded in image Paul E. McKenney
2023-07-08 17:19     ` Alejandro Colomar [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=0b4048d4-e80d-a80c-d16d-3fbb301cf698@kernel.org \
    --to=alx@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=paulmck@kernel.org \
    --cc=vbabka@suse.cz \
    /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