linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Subject: Re: [PATCH bootconfig 3/3] doc: Add /proc/bootconfig to proc.rst
Date: Sat, 7 Oct 2023 10:51:47 +0900	[thread overview]
Message-ID: <20231007105147.9e34656f36a9b3ab090ffe85@kernel.org> (raw)
In-Reply-To: <20231005171747.541123-3-paulmck@kernel.org>

On Thu,  5 Oct 2023 10:17:47 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> Add /proc/bootconfig description to Documentation/filesystems/proc.rst.
> 
> Reported-by: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
>  Documentation/filesystems/proc.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 5703b0e87cbe..a2c160f29632 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -689,6 +689,11 @@ files are there, and which are missing.
>   File         Content
>   ============ ===============================================================
>   apm          Advanced power management info
> + bootconfig   Kernel command line obtained from boot config,
> + 	      and, if there were kernel parameters from the
> +	      boot loader, a "# Parameters from bootloader:"
> +	      line followed by a line containing those
> +	      parameters prefixed by "# ".			(5.5)

Ditto. Curiously, in this part of the document, the tail spaces until "(5.5)"
are using tabs, but the head spaces are using whitespaces. So updated it.
I noticed that a warning message when I imported it to my bootconfig/for-next
branch.

Thank you,

>   buddyinfo    Kernel memory allocator information (see text)	(2.5)
>   bus          Directory containing bus specific information
>   cmdline      Kernel command line, both from bootloader and embedded
> -- 
> 2.40.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2023-10-07  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 17:16 [PATCH bootconfig 0/3] Expose boot-loader kernel command-line arguments Paul E. McKenney
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 [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=20231007105147.9e34656f36a9b3ab090ffe85@kernel.org \
    --to=mhiramat@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=paulmck@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).