From: Masami Hiramatsu <mhiramat@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Elfring <Markus.Elfring@web.de>,
Randy Dunlap <rdunlap@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-doc@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [v4] Documentation: bootconfig: Update boot configuration documentation
Date: Thu, 5 Mar 2020 09:59:17 +0900 [thread overview]
Message-ID: <20200305095917.9cd7c2a7f5f6b492601e27bb@kernel.org> (raw)
In-Reply-To: <20200304142259.7eaa3633@lwn.net>
On Wed, 4 Mar 2020 14:22:59 -0700
Jonathan Corbet <corbet@lwn.net> wrote:
> On Wed, 4 Mar 2020 22:20:07 +0100
> Markus Elfring <Markus.Elfring@web.de> wrote:
>
> > > I'm hoping to be done with the current changes. :)
> >
> > Will a term like “grouping of parent keys” need any additional explanation?
>
> Honestly, Markus, I think that the patch is good enough for now; time to
> merge it and move on to something else.
Thanks Jon,
I'll send the final version soon.
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-03-05 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:05 [PATCH v4 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-03 9:05 ` [PATCH v4] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-03 10:10 ` Markus Elfring
2020-03-04 4:55 ` Randy Dunlap
2020-03-04 11:37 ` Masami Hiramatsu
2020-03-04 14:45 ` [v4] " Markus Elfring
2020-03-04 16:20 ` Randy Dunlap
2020-03-04 18:09 ` Markus Elfring
2020-03-04 21:07 ` Randy Dunlap
2020-03-04 21:20 ` Markus Elfring
2020-03-04 21:22 ` Jonathan Corbet
2020-03-04 21:30 ` Markus Elfring
2020-03-05 0:59 ` Masami Hiramatsu [this message]
2020-03-05 0:58 ` Masami Hiramatsu
2020-03-03 9:50 ` [v4 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=20200305095917.9cd7c2a7f5f6b492601e27bb@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;
as well as URLs for NNTP newsgroup(s).