From: Masami Hiramatsu <mhiramat@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: bootconfig: Update boot configuration documentation
Date: Fri, 28 Feb 2020 22:26:35 +0900 [thread overview]
Message-ID: <20200228222635.96b258bedd2e68141b8a45c9@kernel.org> (raw)
In-Reply-To: <57b79bdd-36f1-c8c3-e1d3-7d21db47a8f3@web.de>
On Fri, 28 Feb 2020 11:00:43 +0100
Markus Elfring <Markus.Elfring@web.de> wrote:
> …
> > +++ b/Documentation/admin-guide/bootconfig.rst
> …
> > +… All sub-keys under "kernel" root key are passed as a part of
> > +kernel command line [1]_, and ones under "init" root key are passed as a part
> > +of init command line. …
>
> Can an enumeration be clearer for this information?
>
> Will the distinction become more interesting for well-known keys?
Your question becomes more meaningless... If you have any such concern,
you can write a patch on it for a contribution. Yes, you can!
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-02-28 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 8:30 [PATCH v2 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-02-28 8:30 ` [PATCH v2] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-02-28 10:00 ` Markus Elfring
2020-02-28 13:26 ` Masami Hiramatsu [this message]
2020-02-28 11:55 ` [v2] " Markus Elfring
2020-02-29 5:59 ` [PATCH v2] " Randy Dunlap
2020-03-02 6:52 ` Masami Hiramatsu
2020-03-02 7:06 ` Randy Dunlap
2020-03-02 8:23 ` [v2] " Markus Elfring
2020-02-28 9:00 ` [v2 0/1] Documentation: bootconfig: Documentation updates Markus Elfring
2020-02-28 13:23 ` Masami Hiramatsu
2020-02-28 14:05 ` Markus Elfring
2020-02-28 14:55 ` 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=20200228222635.96b258bedd2e68141b8a45c9@kernel.org \
--to=mhiramat@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--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).