public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Randy Dunlap <rdunlap@infradead.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 v3] Documentation: bootconfig: Update boot configuration documentation
Date: Tue, 3 Mar 2020 11:56:33 +0900	[thread overview]
Message-ID: <20200303115633.3db043ce643c5bc55915a57c@kernel.org> (raw)
In-Reply-To: <8c032093-c652-5e33-36ad-732f73beabab@infradead.org>

On Mon, 2 Mar 2020 17:52:36 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:

> On 3/2/20 12:03 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 v3:
> >  - Specify that comments also count in size.
> >  - Fix a confusing sentence.
> >  - Add O=<builddir> to make command.
> 
> 
> Hi Masami-san,
> 
> I think that you misunderstood me.  I am asking that you
> make "make O=builddir -C tools/bootconfig" work properly, i.e.,
> the bootconfig binary should be built in the <builddir>.
> 
> Presently when I enter that command, the bootconfig binary
> is still built in the kernel source tree.

Oops, that's my mistake! It needs to be fixed soon.
Thank you for reporting it!

(Also, I misunderstood what O= option means for tools...)

> 
> > Changes in v2:
> >  - Fixes additional typos (Thanks Markus and Randy!)
> >  - Change a section title to "Tree Structured Key".
> > ---
> >  Documentation/admin-guide/bootconfig.rst |  181 +++++++++++++++++++-----------
> >  Documentation/trace/boottime-trace.rst   |    2 
> >  2 files changed, 117 insertions(+), 66 deletions(-)
> > 
> 
> 
> All of the other changes look good to me.

Thank you!



> 
> thanks.
> -- 
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2020-03-03  2:56 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
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 [this message]
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=20200303115633.3db043ce643c5bc55915a57c@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=corbet@lwn.net \
    --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