linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>, linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: bootconfig: Add EBNF syntax file
Date: Thu, 27 Feb 2020 20:53:03 +0100	[thread overview]
Message-ID: <2390b729-1b0b-26b5-66bc-92e40e3467b1@web.de> (raw)
In-Reply-To: <158278836196.14966.3881489301852781521.stgit@devnote2>

Thanks for such a contribution.


> Add an extended Backus–Naur form (EBNF) syntax file for

Can it matter to mention the specific file format specification version
which should be applied finally?

Would you like to refer to any standard variant?


> bootconfig so that user can logically understand how they

Wording alternative “… that users can …”?


> can write correct boot configuration file.

Related development tools provide some benefits then, don't they?



…
> +++ b/Documentation/admin-guide/bootconfig.ebnf
…
> +digit = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;

Can the specification of such alternatives (or value ranges) become
more compact (depending on a selected standard)?


…
> +++ b/Documentation/admin-guide/bootconfig.rst
…
> +Here is the boot configuration file syntax written in EBNF.

I suggest to replace the abbreviation “EBNF” by the term “extended Backus–Naur form”
in such a sentence.

Regards,
Markus

  reply	other threads:[~2020-02-27 19:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  7:25 [PATCH 0/2] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-02-27  7:25 ` [PATCH 1/2] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-02-27 19:12   ` Markus Elfring
2020-02-28  4:36     ` Randy Dunlap
2020-02-28  5:35     ` Masami Hiramatsu
2020-02-28  8:30       ` [1/2] " Markus Elfring
2020-02-28 13:11         ` Masami Hiramatsu
2020-02-28 13:35           ` Markus Elfring
2020-02-28  4:50   ` [PATCH 1/2] " Randy Dunlap
2020-02-28  6:12     ` Masami Hiramatsu
2020-02-27  7:26 ` [PATCH 2/2] Documentation: bootconfig: Add EBNF syntax file Masami Hiramatsu
2020-02-27 19:53   ` Markus Elfring [this message]
2020-02-28  3:15     ` Masami Hiramatsu
2020-02-28  8:46   ` Markus Elfring
2020-02-29  9:00   ` 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=2390b729-1b0b-26b5-66bc-92e40e3467b1@web.de \
    --to=markus.elfring@web.de \
    --cc=corbet@lwn.net \
    --cc=kernel-janitors@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).