All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH v5] Documentation: bootconfig: Update boot configuration documentation
Date: Thu, 5 Mar 2020 19:32:49 +0900	[thread overview]
Message-ID: <20200305193249.4c5f993bb52e5874cd2df627@kernel.org> (raw)
In-Reply-To: <ef820445-25c5-a312-57d4-25ff3b4d08cf@infradead.org>

On Wed, 4 Mar 2020 23:01:21 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:

> On 3/4/20 10:44 PM, Masami Hiramatsu wrote:
> > Update boot configuration documentation.
> > 
> >  - Not using "config" abbreviation but configuration or description.
> >  - Rewrite descriptions of node and its maxinum number.
> >  - Add a section of use cases of boot configuration.
> >  - Move how to use bootconfig to earlier section.
> >  - Fix some typos, indents and format mistakes.
> > 
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> 
> Hi Masami,
> 
> I swear that I am not trying to cause another version...

Oh, no problem. I'll go along with your reviews.

> 
> > ---
> > Changes in v5:
> >  - Elaborate the document.
> >  - Fix some typos.
> > Changes in v4:
> >  - Remove O= option from examples.
> > Changes in v3:
> >  - Specify that comments also count in size.
> >  - Fix a confusing sentence.
> >  - Add O=<builddir> to make command.
> > Changes in v2:
> >  - Fixes additional typos (Thanks Markus and Randy!)
> >  - Change a section title to "Tree Structured Key".
> > ---
> >  Documentation/admin-guide/bootconfig.rst |  201 +++++++++++++++++++-----------
> >  Documentation/trace/boottime-trace.rst   |    2 
> >  2 files changed, 131 insertions(+), 72 deletions(-)
> > 
> > diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
> > index cf2edcd09183..3bfc9ddf68e1 100644
> > --- a/Documentation/admin-guide/bootconfig.rst
> > +++ b/Documentation/admin-guide/bootconfig.rst
> > @@ -11,25 +11,106 @@ Boot Configuration
> 
> > +When to Use the Boot Configuration?
> > +-----------------------------------
> > +
> > +The boot configuration supports kernel command line options and init daemon
> > +boot options. All sub-keys under "kernel" root key are passed as a part of
> > +the kernel command line [1]_, and ones under "init" root key are passed as
> > +a part of the init daemon's command line. For example, ::
> > +
> > +   root=UUID=8cd79b08-bda0-4b9d-954c-5d5f34b98c82 ro quiet splash console=ttyS0,115200n8 console=tty0
> > +
> > +This can be written as following boot configuration file.::
> > +
> > +   kernel {
> > +      root = "UUID=8cd79b08-bda0-4b9d-954c-5d5f34b98c82" # nvme0n1p3
> > +      ro       # mount rootfs as read only
> > +      quiet    # No console log
> > +      splash   # show splash image on boot screen
> > +      console = "ttyS0,115200n8" # 1st console to serial device
> > +      console += tty0            # add 2nd console
> > +   }
> > +
> > +If you think that kernel/init options becomes too long to write in boot-loader
> 
>                                          become

OK.

> 
> > +configuration file or you want to comment on each option, the boot
> > +configuration may be suitable. If unsure, you can still continue to use the
> > +legacy kernel command line.
> 
> 
> > +Boot Configuration Syntax
> > +=========================
> > +
> > +The boot configuration syntax is a simple structured key-value. Each key
> > +consists of dot-connected-words, and key and value are connected by ``=``.
> > +The value has to be terminated by semicolon (``;``) or newline (``\n``).
> > +For an array, its entries are separated by comma (``,``). ::
> > +
> > +  KEY[.WORD[...]] = VALUE[, VALUE2[...]][;]
> >  
> >  Unlike the kernel command line syntax, spaces are OK around the comma and ``=``.
> >  
> >  Each key word must contain only alphabets, numbers, dash (``-``) or underscore
> >  (``_``). And each value only contains printable characters or spaces except
> > -for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
> > +for delimiters such as semicolon (``;``), new-line (``\n``), comma (``,``),
> 
>             usually called:                  newline

Yeah, I wonder why I have written so...

> 
> >  hash (``#``) and closing brace (``}``).
> >  
> >  If you want to use those delimiters in a value, you can use either double-
> 
> 
> >  Comments
> >  --------
> >  
> > -The config syntax accepts shell-script style comments. The comments starting
> > -with hash ("#") until newline ("\n") will be ignored.
> > -
> > -::
> > +The boot configuration accepts shell-script style comments. The comments,
> > +beginning with hash (``#``) continues until newline (``\n``), will be
> 
>                                and continuing until newline

OK.

> 
> > +skipped.::
> >  
> >   # comment line
> >   foo = value # value is set to foo.
> 
> 
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thank you!

-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2020-03-05 10:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:44 [PATCH v5 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-05  6:44 ` [PATCH v5] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-05  7:01   ` Randy Dunlap
2020-03-05  9:33     ` [v5] " Markus Elfring
2020-03-05 16:06       ` Randy Dunlap
2020-03-05 17:30         ` Markus Elfring
2020-03-05 17:48           ` Randy Dunlap
2020-03-05 17:56             ` Markus Elfring
2020-03-05 18:39               ` Randy Dunlap
2020-03-05 18:43                 ` Markus Elfring
2020-03-05 18:57                   ` Randy Dunlap
2020-03-05 19:06                     ` Markus Elfring
2020-03-05 19:19                       ` Randy Dunlap
2020-03-05 19:34                         ` Markus Elfring
2020-03-05 19:26                       ` Steven Rostedt
2020-03-05 20:26                         ` Markus Elfring
2020-03-05 20:57                           ` Steven Rostedt
2020-03-05 19:00                   ` Steven Rostedt
2020-03-05 19:14                     ` Markus Elfring
2020-03-05 19:25                       ` Steven Rostedt
2020-03-05 20:10                         ` Markus Elfring
2020-03-05 20:56                           ` Steven Rostedt
2020-03-05 21:26                             ` Markus Elfring
2020-03-05 10:32     ` Masami Hiramatsu [this message]
2020-03-05 13:36     ` [PATCH v5.1] " Masami Hiramatsu
2020-03-05 14:00       ` Markus Elfring
2020-03-05 14:00         ` Markus Elfring
2020-03-06  1:51         ` Masami Hiramatsu
2020-03-06  1:51           ` Masami Hiramatsu
2020-03-06  9:34           ` Markus Elfring
2020-03-06  9:34             ` Markus Elfring
2020-03-06 14:04             ` Masami Hiramatsu
2020-03-06 14:04               ` Masami Hiramatsu
2020-03-06 18:14               ` [v5.1] " Markus Elfring
2020-03-06 18:14                 ` Markus Elfring
2020-03-06 18:40               ` Markus Elfring
2020-03-06 18:40                 ` Markus Elfring
2020-03-14  8:45       ` [PATCH v5.1] " Markus Elfring
2020-03-05  9:22   ` [PATCH v5] " Markus Elfring
2020-03-05  9:22     ` Markus Elfring
2020-03-05 10:19   ` Markus Elfring
2020-03-05 16:07     ` Randy Dunlap
2020-03-05  9:10 ` [v5 0/1] Documentation: bootconfig: Documentation updates Markus Elfring

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=20200305193249.4c5f993bb52e5874cd2df627@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.