From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Namhyung Kim <namhyung@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tim Bird <Tim.Bird@sony.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [for-next][12/26] Documentation: bootconfig: Add a doc for extended boot config
Date: Fri, 21 Feb 2020 16:43:32 +0000 [thread overview]
Message-ID: <5ade73b0-a3e8-e71a-3685-6485f37ac8b7@web.de> (raw)
In-Reply-To: <20200221191637.e9eed4268ff607a98200628c@kernel.org>
>> Is there a need to separate the number from the following unit?
>
> Sorry, I couldn't understand what you pointed here.
Can the specification “… size is 32 KiB …”be more appropriate
(besides a small wording adjustment)?
> Like "descriptions of ..." ?
I got another idea also for the provided documentation format.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/admin-guide/bootconfig.rst?id=bee46b309a13ca158c99c325d0408fb2f0db207f#n18
* Will a file format description become helpful in the way of
an extended Backus–Naur form?
* How will data processing evolve around the added structures?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Namhyung Kim <namhyung@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tim Bird <Tim.Bird@sony.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [for-next][12/26] Documentation: bootconfig: Add a doc for extended boot config
Date: Fri, 21 Feb 2020 17:43:32 +0100 [thread overview]
Message-ID: <5ade73b0-a3e8-e71a-3685-6485f37ac8b7@web.de> (raw)
In-Reply-To: <20200221191637.e9eed4268ff607a98200628c@kernel.org>
>> Is there a need to separate the number from the following unit?
>
> Sorry, I couldn't understand what you pointed here.
Can the specification “… size is 32 KiB …”be more appropriate
(besides a small wording adjustment)?
> Like "descriptions of ..." ?
I got another idea also for the provided documentation format.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/admin-guide/bootconfig.rst?id=bee46b309a13ca158c99c325d0408fb2f0db207f#n18
* Will a file format description become helpful in the way of
an extended Backus–Naur form?
* How will data processing evolve around the added structures?
Regards,
Markus
next prev parent reply other threads:[~2020-02-21 16:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 9:10 [for-next][PATCH 12/26] Documentation: bootconfig: Add a doc for extended boot config Markus Elfring
2020-02-20 9:10 ` Markus Elfring
2020-02-20 13:13 ` Masami Hiramatsu
2020-02-20 13:13 ` Masami Hiramatsu
2020-02-20 15:00 ` Markus Elfring
2020-02-20 15:00 ` Markus Elfring
2020-02-21 10:16 ` Masami Hiramatsu
2020-02-21 10:16 ` Masami Hiramatsu
2020-02-21 16:43 ` Markus Elfring [this message]
2020-02-21 16:43 ` [for-next][12/26] " Markus Elfring
2020-02-22 4:18 ` Masami Hiramatsu
2020-02-22 4:18 ` Masami Hiramatsu
2020-02-22 9:48 ` Markus Elfring
2020-02-22 9:48 ` Markus Elfring
2020-02-22 15:56 ` Masami Hiramatsu
2020-02-22 15:56 ` Masami Hiramatsu
2020-02-22 16:15 ` Markus Elfring
2020-02-22 16:15 ` Markus Elfring
2020-02-24 3:13 ` Masami Hiramatsu
2020-02-24 3:13 ` Masami Hiramatsu
2020-02-24 10:00 ` Markus Elfring
2020-02-24 10:00 ` Markus Elfring
2020-02-25 6:49 ` Masami Hiramatsu
2020-02-25 6:49 ` Masami Hiramatsu
2020-02-25 7:56 ` Markus Elfring
2020-02-25 7:56 ` Markus Elfring
2020-02-25 10:29 ` Masami Hiramatsu
2020-02-25 10:29 ` Masami Hiramatsu
2020-02-25 11:10 ` Markus Elfring
2020-02-25 11:10 ` 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=5ade73b0-a3e8-e71a-3685-6485f37ac8b7@web.de \
--to=markus.elfring@web.de \
--cc=Tim.Bird@sony.com \
--cc=acme@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=torvalds@linux-foundation.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.