From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>, linux-doc@vger.kernel.org
Cc: 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 v3] Documentation: bootconfig: Update boot configuration documentation
Date: Mon, 2 Mar 2020 10:10:08 +0100 [thread overview]
Message-ID: <385d2d20-5f5d-529f-471c-89d0b4c3efd7@web.de> (raw)
In-Reply-To: <158313622831.3082.8237132211731864948.stgit@devnote2>
…
> +++ b/Documentation/admin-guide/bootconfig.rst
…
> +If you think that kernel/init options becomes too long to write in boot-loader
> +configuration file or you want to comment on each option, the boot
> +configuration may be suitable.
I have got still understanding difficulties for this wording.
How do you choose to distribute settings between the mentioned places?
> +Also, some features may depend on the boot configuration, and it has own
> +root key.
Will the key hierarchy need any further clarification?
> + # make O=<builddir> -C tools/bootconfig
Can the order of these parameters matter?
> +The boot configuration syntax is a simple structured key-value.
Would you like to discuss any extensions for such software?
Regards,
Markus
next prev parent reply other threads:[~2020-03-02 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:03 [PATCH v3 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-02 8:03 ` [PATCH v3] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-02 9:10 ` Markus Elfring [this message]
2020-03-02 19:50 ` Jonathan Corbet
2020-03-02 20:08 ` Steven Rostedt
2020-03-02 20:13 ` Jonathan Corbet
2020-03-02 20:19 ` Steven Rostedt
2020-03-03 2:58 ` Masami Hiramatsu
2020-03-03 1:52 ` Randy Dunlap
2020-03-03 2:56 ` Masami Hiramatsu
2020-03-03 6:52 ` [v3] " Markus Elfring
2020-03-03 7:51 ` Randy Dunlap
2020-03-03 9:46 ` Markus Elfring
2020-03-02 8:33 ` [v3 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=385d2d20-5f5d-529f-471c-89d0b4c3efd7@web.de \
--to=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=mhiramat@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
all inboxes | Powered by JetHome®