linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: 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, alx@kernel.org,
	linux-man@vger.kernel.org
Subject: Re: [PATCH] proc.5: Clarify that boot arguments can be embedded in image
Date: Wed, 5 Jul 2023 13:33:35 -0700	[thread overview]
Message-ID: <d3057de8-39ca-4d2a-aa03-9134f916fac9@paulmck-laptop> (raw)
In-Reply-To: <20230704215932.c9cab0af086528e52ca0bfbb@kernel.org>

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>

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>
> > 
> > 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>

  reply	other threads:[~2023-07-05 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 23:33 [PATCH] proc.5: Clarify that boot arguments can be embedded in image Paul E. McKenney
2023-07-04 12:59 ` Masami Hiramatsu
2023-07-05 20:33   ` Paul E. McKenney [this message]
2023-07-08 17:19     ` Alejandro Colomar
2023-07-04  6:25 S. Isaeiela C. Escobar D. Anktnktr

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=d3057de8-39ca-4d2a-aa03-9134f916fac9@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alx@kernel.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=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;
as well as URLs for NNTP newsgroup(s).