[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <23e371ca-5df8-3ae3-c685-b01c07b55540@web.de>
Date: Thu, 20 Feb 2020 10:10:20 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Masami Hiramatsu <mhiramat@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
linux-doc@...r.kernel.org, linux-fsdevel@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ingo Molnar <mingo@...hat.com>, Jiri Olsa <jolsa@...hat.com>,
Jonathan Corbet <corbet@....net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Namhyung Kim <namhyung@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>,
Rob Herring <robh+dt@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Tim Bird <Tim.Bird@...y.com>,
Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: Re: [for-next][PATCH 12/26] Documentation: bootconfig: Add a doc for
extended boot config
I wonder about a few details in the added text.
…
> +++ b/Documentation/admin-guide/bootconfig.rst
…
> +C onfig File Limitation
How do you think about to omit a space character at the beginning
of this line?
> +Currently the maximum config size size is 32KB …
Would you like to avoid a word duplication here?
> +Note: this is not the number of entries but nodes, an entry must consume
> +more than 2 nodes (a key-word and a value). …
I find the relevance of the term “nodes” unclear at the moment.
Could an other wording be nicer than the abbreviation “a doc for … config”
in the commit subject?
Regards,
Markus
Powered by blists - more mailing lists