From: Markus Elfring <Markus.Elfring@web.de>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org
Subject: Re: [v5] Documentation: bootconfig: Update boot configuration documentation
Date: Thu, 5 Mar 2020 18:56:45 +0100 [thread overview]
Message-ID: <dbef7b77-945a-585e-12fe-b5e30eb1a6bc@web.de> (raw)
In-Reply-To: <997f73af-dc6c-bc8b-12ba-69270ee4b95d@infradead.org>
> If you would (could) be more concrete (or discrete) in your suggestions,
> I would be glad to comment on them.
Does this view indicate any communication difficulties?
Which of the possibly unanswered issues do you find not concrete enough so far?
Regards,
Markus
next prev parent reply other threads:[~2020-03-05 17:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:44 [PATCH v5 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-05 6:44 ` [PATCH v5] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-05 7:01 ` Randy Dunlap
2020-03-05 9:33 ` [v5] " Markus Elfring
2020-03-05 16:06 ` Randy Dunlap
2020-03-05 17:30 ` Markus Elfring
2020-03-05 17:48 ` Randy Dunlap
2020-03-05 17:56 ` Markus Elfring [this message]
2020-03-05 18:39 ` Randy Dunlap
2020-03-05 18:43 ` Markus Elfring
2020-03-05 18:57 ` Randy Dunlap
2020-03-05 19:06 ` Markus Elfring
2020-03-05 19:19 ` Randy Dunlap
2020-03-05 19:34 ` Markus Elfring
2020-03-05 19:26 ` Steven Rostedt
2020-03-05 20:26 ` Markus Elfring
2020-03-05 20:57 ` Steven Rostedt
2020-03-05 19:00 ` Steven Rostedt
2020-03-05 19:14 ` Markus Elfring
2020-03-05 19:25 ` Steven Rostedt
2020-03-05 20:10 ` Markus Elfring
2020-03-05 20:56 ` Steven Rostedt
2020-03-05 21:26 ` Markus Elfring
2020-03-05 10:32 ` [PATCH v5] " Masami Hiramatsu
2020-03-05 13:36 ` [PATCH v5.1] " Masami Hiramatsu
2020-03-05 14:00 ` Markus Elfring
2020-03-06 1:51 ` Masami Hiramatsu
2020-03-06 9:34 ` Markus Elfring
2020-03-06 14:04 ` Masami Hiramatsu
2020-03-06 18:14 ` [v5.1] " Markus Elfring
2020-03-06 18:40 ` Markus Elfring
2020-03-14 8:45 ` [PATCH v5.1] " Markus Elfring
2020-03-05 9:22 ` [PATCH v5] " Markus Elfring
2020-03-05 10:19 ` Markus Elfring
2020-03-05 16:07 ` Randy Dunlap
2020-03-05 9:10 ` [v5 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=dbef7b77-945a-585e-12fe-b5e30eb1a6bc@web.de \
--to=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=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
all inboxes | Powered by JetHome®