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: [1/2] Documentation: bootconfig: Update boot configuration documentation
Date: Fri, 28 Feb 2020 09:30:27 +0100 [thread overview]
Message-ID: <efe38d09-e73d-97b3-d4be-79194ab2685f@web.de> (raw)
In-Reply-To: <20200228143528.209db45e5f0f78474ef83387@kernel.org>
>>> +Also, some subsystem may depend on the boot configuration, and it has own
>>> +root key.
>>
>> Would you like to explain the influence of a key hierarchy any further?
>
> Please read the example (boot time tracer) carefully :)
I find the descriptions still too terse for corresponding relationships.
>> * Can such system limits become more configurable?
>
> No.
The possibility remains to adjust the source code also for special needs.
>>> +(Note: Each key consists of words separated by dot, and value also consists
>>> +of values separated by comma. Here, each word and each value is generally
>>> +called a "node".)
>>
>> I would prefer the interpretation that nodes contain corresponding attributes.
>
> No. Node is a node. It is merely generic.
I hope that the applied ontology will be clarified a bit more.
>> How do you think about to add a link to a formal file format description?
>
> Oh, nice idea. Please contribute it :)
Did you provide it (according to a RST include directive in the subsequent
update step)?
Can it be helpful to reorder any changes for the discussed patch series?
Regards,
Markus
next prev parent reply other threads:[~2020-02-28 8:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 7:25 [PATCH 0/2] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-02-27 7:25 ` [PATCH 1/2] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-02-27 19:12 ` Markus Elfring
2020-02-28 4:36 ` Randy Dunlap
2020-02-28 5:35 ` Masami Hiramatsu
2020-02-28 8:30 ` Markus Elfring [this message]
2020-02-28 13:11 ` [1/2] " Masami Hiramatsu
2020-02-28 13:35 ` Markus Elfring
2020-02-28 4:50 ` [PATCH 1/2] " Randy Dunlap
2020-02-28 6:12 ` Masami Hiramatsu
2020-02-27 7:26 ` [PATCH 2/2] Documentation: bootconfig: Add EBNF syntax file Masami Hiramatsu
2020-02-27 19:53 ` Markus Elfring
2020-02-28 3:15 ` Masami Hiramatsu
2020-02-28 8:46 ` Markus Elfring
2020-02-29 9:00 ` 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=efe38d09-e73d-97b3-d4be-79194ab2685f@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;
as well as URLs for NNTP newsgroup(s).