linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Subject: [PATCH bootconfig 0/3] Expose boot-loader kernel command-line arguments
Date: Thu, 5 Oct 2023 10:16:45 -0700	[thread overview]
Message-ID: <6ea609a4-12e3-4266-8816-b9fca1f1f21c@paulmck-laptop> (raw)

Hello!

This series contains bootconfig updates that make the kernel command-line
arguments that came from the bootloader (excluding those from bootconfig)
visible as a comment in the existing /proc/bootconfig file.  It also
updates documentation.

1.	Update /proc/cmdline documentation to include boot config.

2.	fs/proc: Add boot loader arguments as comment to /proc/bootconfig.

3.	Add /proc/bootconfig to proc.rst.

						Thanx, Paul

------------------------------------------------------------------------

 Documentation/filesystems/proc.rst   |    5 +++++
 b/Documentation/filesystems/proc.rst |    3 ++-
 b/fs/proc/bootconfig.c               |    6 ++++++
 3 files changed, 13 insertions(+), 1 deletion(-)

             reply	other threads:[~2023-10-05 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 17:16 Paul E. McKenney [this message]
2023-10-05 17:17 ` [PATCH bootconfig 1/3] doc: Update /proc/cmdline documentation to include boot config Paul E. McKenney
2023-10-07  1:48   ` Masami Hiramatsu
2023-10-05 17:17 ` [PATCH bootconfig 2/3] fs/proc: Add boot loader arguments as comment to /proc/bootconfig Paul E. McKenney
2023-10-06  8:59   ` Masami Hiramatsu
2023-10-06 16:52     ` Paul E. McKenney
2023-10-07  1:42       ` Masami Hiramatsu
2023-10-07  3:42         ` Paul E. McKenney
2023-10-05 17:17 ` [PATCH bootconfig 3/3] doc: Add /proc/bootconfig to proc.rst Paul E. McKenney
2023-10-07  1:51   ` Masami Hiramatsu

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=6ea609a4-12e3-4266-8816-b9fca1f1f21c@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@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).