public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@infradead.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: Mon, 2 Mar 2020 12:50:33 -0700	[thread overview]
Message-ID: <20200302125033.4a62e88e@lwn.net> (raw)
In-Reply-To: <158313622831.3082.8237132211731864948.stgit@devnote2>

On Mon,  2 Mar 2020 17:03:48 +0900
Masami Hiramatsu <mhiramat@kernel.org> 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.
> Changes in v2:
>  - Fixes additional typos (Thanks Markus and Randy!)
>  - Change a section title to "Tree Structured Key".
> ---

So I tried to apply this but failed - it's built on other changes to
bootconfig.rst that went into linux-next via Steve's tree.  So Steve,
would you like to take this one too?

Thanks,

jon

  parent reply	other threads:[~2020-03-02 19:50 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 [this message]
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=20200302125033.4a62e88e@lwn.net \
    --to=corbet@lwn.net \
    --cc=Markus.Elfring@web.de \
    --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