All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH v2] Documentation: bootconfig: Update boot configuration documentation
Date: Sun, 1 Mar 2020 23:06:48 -0800	[thread overview]
Message-ID: <2080a377-f03d-9df6-bb4a-c440d6f8ac11@infradead.org> (raw)
In-Reply-To: <20200302155247.93558d4865a8bcd160ef39e5@kernel.org>

On 3/1/20 10:52 PM, Masami Hiramatsu wrote:
> On Fri, 28 Feb 2020 21:59:45 -0800
> Randy Dunlap <rdunlap@infradead.org> wrote:
> 
>> On 2/28/20 12:30 AM, Masami Hiramatsu wrote:
>>> Update boot configuration documentation.
>>>
>>>  - Not using "config" abbreviation but configuration or description.
>>>  - Rewrite descriptions of node and its maxinum number.
>>>  - Add a section of use cases of boot configuration.
>>>  - Move how to use bootconfig to earlier section.
>>>  - Fix some typos, indents and format mistakes.
>>>
>>> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
>>> ---
>>> Changes in v2:
>>>  - Fixes additional typos (Thanks Markus and Randy!)
>>>  - Change a section title to "Tree Structured Key".
>>> ---
>>>  Documentation/admin-guide/bootconfig.rst |  180 +++++++++++++++++++-----------
>>>  Documentation/trace/boottime-trace.rst   |    2 
>>>  2 files changed, 116 insertions(+), 66 deletions(-)


>>> +Also, some subsystem may depend on the boot configuration, and it has own
>>> +root key. For example, ftrace boot-time tracer uses "ftrace" root key to
>>> +describe its options [2]_. In this case, you need to use the boot
>>> +configuration.
>>
>> Does this say that "ftrace" requires use of bootconfig?
>> It seems to say that.
> 
> Ah, I got it. The last sentence is confusing. How about below?
> 
> "If you want to use the boot-time tracer, you need to use the boot configuration."

Yes, that is better. Thanks.

-- 
~Randy


  reply	other threads:[~2020-03-02  7:06 UTC|newest]

Thread overview: 21+ 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 10:00     ` Markus Elfring
2020-02-28 13:26     ` Masami Hiramatsu
2020-02-28 13:26       ` Masami Hiramatsu
2020-02-28 11:55   ` [v2] " Markus Elfring
2020-02-28 11:55     ` 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 [this message]
2020-03-02  8:23       ` [v2] " Markus Elfring
2020-03-02  8:23         ` Markus Elfring
2020-02-28  9:00 ` [v2 0/1] Documentation: bootconfig: Documentation updates Markus Elfring
2020-02-28  9:00   ` Markus Elfring
2020-02-28 13:23   ` Masami Hiramatsu
2020-02-28 13:23     ` Masami Hiramatsu
2020-02-28 14:05     ` Markus Elfring
2020-02-28 14:05       ` Markus Elfring
2020-02-28 14:55       ` Masami Hiramatsu
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=2080a377-f03d-9df6-bb4a-c440d6f8ac11@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Markus.Elfring@web.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.