From: Masami Hiramatsu <mhiramat@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
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: Sat, 22 Feb 2020 04:18:33 +0000 [thread overview]
Message-ID: <20200222131833.56a5be2d36033dc5a77a9f0b@kernel.org> (raw)
In-Reply-To: <5ade73b0-a3e8-e71a-3685-6485f37ac8b7@web.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1067 bytes --]
On Fri, 21 Feb 2020 17:43:32 +0100
Markus Elfring <Markus.Elfring@web.de> wrote:
> >> 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)?
OK, I'll update as so :)
> > 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¾e46b309a13ca158c99c325d0408fb2f0db207f#n18
>
> * Will a file format description become helpful in the way of
> an extended Backus–Naur form?
Good suggestion! Let me try to write an EBNF section.
I think EBNF can logically explain the format, but not intuitive
- we need some examples.
> * How will data processing evolve around the added structures?
OK, I'll add some more API (and usage) differences from the legacy
command line.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
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: Sat, 22 Feb 2020 13:18:33 +0900 [thread overview]
Message-ID: <20200222131833.56a5be2d36033dc5a77a9f0b@kernel.org> (raw)
In-Reply-To: <5ade73b0-a3e8-e71a-3685-6485f37ac8b7@web.de>
On Fri, 21 Feb 2020 17:43:32 +0100
Markus Elfring <Markus.Elfring@web.de> wrote:
> >> 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)?
OK, I'll update as so :)
> > 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?
Good suggestion! Let me try to write an EBNF section.
I think EBNF can logically explain the format, but not intuitive
- we need some examples.
> * How will data processing evolve around the added structures?
OK, I'll add some more API (and usage) differences from the legacy
command line.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-02-22 4:18 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 ` [for-next][12/26] " Markus Elfring
2020-02-21 16:43 ` Markus Elfring
2020-02-22 4:18 ` Masami Hiramatsu [this message]
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=20200222131833.56a5be2d36033dc5a77a9f0b@kernel.org \
--to=mhiramat@kernel.org \
--cc=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=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.