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: [1/2] Documentation: bootconfig: Update boot configuration documentation
Date: Fri, 28 Feb 2020 14:35:05 +0100 [thread overview]
Message-ID: <44efe433-c1f5-9131-4b0e-50cc5897a4f3@web.de> (raw)
In-Reply-To: <20200228221108.ff392be76fee6925f27103e6@kernel.org>
>>>> How do you think about to add a link to a formal file format description?
>>>
>>> Oh, nice idea. Please contribute it :)
>>
>> Did you provide it (according to a RST include directive in the subsequent
>> update step)?
>
> No I didn't.
I hope that more progress can be achieved around the published suggestion
“bootconfig: Add EBNF syntax file”.
https://lore.kernel.org/linux-doc/158278836196.14966.3881489301852781521.stgit@devnote2/
https://lore.kernel.org/patchwork/patch/1200987/
https://lkml.org/lkml/2020/2/27/72
> I you think that is important, feel free to write up.
I am curious how the software development attention will evolve further.
> You have a parser code in the kernel already.
This software component is useful there.
> It might be not hard for you. :)
Some challenges are waiting on corresponding solutions.
Regards,
Markus
next prev parent reply other threads:[~2020-02-28 13:35 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 [this message]
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
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=44efe433-c1f5-9131-4b0e-50cc5897a4f3@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
all inboxes | Powered by JetHome®