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 v4] Documentation: bootconfig: Update boot configuration documentation
Date: Wed, 4 Mar 2020 20:37:22 +0900 [thread overview]
Message-ID: <20200304203722.8e8699c2a3e0a979aae091b1@kernel.org> (raw)
In-Reply-To: <ad1e9855-4c64-53bd-7da5-f7cdafe78571@infradead.org>
Hi Randy,
Thanks for review and good suggestions!
On Tue, 3 Mar 2020 20:55:39 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> > +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 semi-colon (``;``) or newline (``\n``).
> > For array value, array entries are separated by comma (``,``). ::
>
> values,
> or just
> For an array, its entries are separated by
I like this latter one.
[...]
> > +Tree Structured Key
> > +-------------------
> >
> > -The boot config file syntax allows user to merge partially same word keys
> > -by brace. For example::
> > +The boot configuration syntax allows user to merge same parent key using
>
> allows the user
> although I am having problems with the rest of that sentence.
What about the following?
User can group identical parent keys together and use braces to list child keys
under them.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-03-04 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:05 [PATCH v4 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-03 9:05 ` [PATCH v4] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-03 10:10 ` Markus Elfring
2020-03-04 4:55 ` Randy Dunlap
2020-03-04 11:37 ` Masami Hiramatsu [this message]
2020-03-04 14:45 ` [v4] " Markus Elfring
2020-03-04 16:20 ` Randy Dunlap
2020-03-04 18:09 ` Markus Elfring
2020-03-04 21:07 ` Randy Dunlap
2020-03-04 21:20 ` Markus Elfring
2020-03-04 21:22 ` Jonathan Corbet
2020-03-04 21:30 ` Markus Elfring
2020-03-05 0:59 ` Masami Hiramatsu
2020-03-05 0:58 ` Masami Hiramatsu
2020-03-03 9:50 ` [v4 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=20200304203722.8e8699c2a3e0a979aae091b1@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 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).