lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 Feb 2020 16:00:23 +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 >>> +Currently the maximum config size size is 32KB … >> >> Would you like to avoid a word duplication here? > > Oops, still exist. Is there a need to separate the number from the following unit? > Indeed, "node" is not well defined. What about this? > --- > Each key consists of words separated by dot, and value also consists of > values separated by comma. Here, each word and each value is generally > called a "node". I have got still understanding difficulties with such an interpretation. * Do other contributors find an other word also more appropriate for this use case? * How will the influence evolve for naming these items? * Is each element just a string (according to specific rules)? >> Could an other wording be nicer than the abbreviation “a doc for … config” >> in the commit subject? > > OK, I'll try next time. Will words like “descriptions”and “configuration”be helpful? Regards, Markus
Powered by blists - more mailing lists