[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <385d2d20-5f5d-529f-471c-89d0b4c3efd7@web.de>
Date: Mon, 2 Mar 2020 10:10:08 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Masami Hiramatsu <mhiramat@...nel.org>, linux-doc@...r.kernel.org
Cc: Jonathan Corbet <corbet@....net>,
Steven Rostedt <rostedt@...dmis.org>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v3] Documentation: bootconfig: Update boot configuration
documentation
…
> +++ 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
Powered by blists - more mailing lists