From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: bootconfig: Add EBNF definiton of bootconfig
Date: Sat, 14 Mar 2026 18:34:38 +0900 [thread overview]
Message-ID: <20260314183438.2babb627d8a58290f20be111@kernel.org> (raw)
In-Reply-To: <177347919991.458550.13051415412509206815.stgit@devnote2>
On Sat, 14 Mar 2026 18:06:40 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Add the EBNF definition to Documentation/admin-guide/bootconfig.rst
> to formally define the bootconfig syntax.
>
Wait, I rethink it may be better to be a separated section
so that it can be referred easily.
Let me update it.
Thanks,
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> Documentation/admin-guide/bootconfig.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
> index f712758472d5..5c5f736ca982 100644
> --- a/Documentation/admin-guide/bootconfig.rst
> +++ b/Documentation/admin-guide/bootconfig.rst
> @@ -22,6 +22,21 @@ The boot config syntax is a simple structured key-value. Each key consists
> of dot-connected-words, and key and value are connected by ``=``. The value
> string has to be terminated by the following delimiters described below.
>
> +The syntax is defined in EBNF as follows::
> +
> + Config = { Statement }
> + Statement = [ Key [ Assignment | Block ] | Comment ] ( "\n" | ";" )
> + Assignment = ( "=" | "+=" | ":=" ) ValueList
> + ValueList = [ Value { "," [ { ( Comment | "\n" ) } ] Value } ]
> + Block = "{" { Statement } "}"
> + Key = Word { "." Word }
> + Word = [a-zA-Z0-9_-]+
> + Value = QuotedValue | UnquotedValue
> + QuotedValue = "\"" { any_character_except_double_quote } "\""
> + | "'" { any_character_except_single_quote } "'"
> + UnquotedValue = { any_printable_character_except_delimiters }
> + Comment = "#" { any_character_except_newline }
> +
> Each key word must contain only alphabets, numbers, dash (``-``) or underscore
> (``_``). And each value only contains printable characters or spaces except
> for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-03-14 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 9:06 [PATCH 0/2] bootconfig: Add EBNF definition and more tests Masami Hiramatsu (Google)
2026-03-14 9:06 ` [PATCH 1/2] Documentation: bootconfig: Add EBNF definiton of bootconfig Masami Hiramatsu (Google)
2026-03-14 9:34 ` Masami Hiramatsu [this message]
2026-03-14 9:06 ` [PATCH 2/2] bootconfig: Add more test samples Masami Hiramatsu (Google)
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=20260314183438.2babb627d8a58290f20be111@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.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