linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [v5] Documentation: bootconfig: Update boot configuration documentation
Date: Thu, 5 Mar 2020 22:26:32 +0100	[thread overview]
Message-ID: <7976cd6c-da28-2df7-492f-7d412e40ff5e@web.de> (raw)
In-Reply-To: <20200305155628.09a1e1d4@gandalf.local.home>

>>> What bug are you reporting?
>>
>> Examples:
>>
>> * Another typo
>>   “… contain only alphabets, …”
>>   https://lore.kernel.org/linux-doc/967d6fee-e0cd-c53f-c1f6-b367a979762c@web.de/
>>   https://lkml.org/lkml/2020/3/5/247
>
> Legitimate but not critical.

Thanks for such a view.

It might be that less simple update candidates were left over now.



>> * Use case explanation
>>   https://lore.kernel.org/linux-doc/f3c51b0a-2a55-6523-96e2-4f9ef0635d9f@web.de/
>>   https://lkml.org/lkml/2020/3/5/429
>
> I believe what Masami has is sufficient.

I got an other impression.

An other document contains background information like the following.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/trace/boottime-trace.rst?id=b8381ce7aa8ef1ab5a79bf710508e504c494acf7
“…
Since kernel command line is not enough to control these complex features,
this uses bootconfig file to describe tracing feature programming.
…”



>> * Challenges for the safe application of key hierarchies
>>   “kernel.ftrace”?
>>   https://lore.kernel.org/linux-doc/c4a0bc10-a38b-6ea9-e125-7a37f667e61a@web.de/
>>   https://lkml.org/lkml/2020/2/28/363
>
> Again, what Masami has is sufficient.

I would appreciate further clarification also in this area.


>> * Feature request for syntax description
>>   https://lore.kernel.org/linux-doc/2390b729-1b0b-26b5-66bc-92e40e3467b1@web.de/
>>   https://lkml.org/lkml/2020/2/27/1869
>
> Masami's reply to you was sufficient.

Yes (in principle).

But I hope to achieve collateral evolution here, too.


> Of your examples, only one do I see can be applied, but is just a minor
> change in wording.

I am trying again to resolve disagreements somehow.


> I don't know where you are going with this, and unless you plan on
> submitting patches, I think this document is complete as is.

I hope also to influence the software development attention another bit.

Regards,
Markus

  reply	other threads:[~2020-03-05 21:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:44 [PATCH v5 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-03-05  6:44 ` [PATCH v5] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-03-05  7:01   ` Randy Dunlap
2020-03-05  9:33     ` [v5] " Markus Elfring
2020-03-05 16:06       ` Randy Dunlap
2020-03-05 17:30         ` Markus Elfring
2020-03-05 17:48           ` Randy Dunlap
2020-03-05 17:56             ` Markus Elfring
2020-03-05 18:39               ` Randy Dunlap
2020-03-05 18:43                 ` Markus Elfring
2020-03-05 18:57                   ` Randy Dunlap
2020-03-05 19:06                     ` Markus Elfring
2020-03-05 19:19                       ` Randy Dunlap
2020-03-05 19:34                         ` Markus Elfring
2020-03-05 19:26                       ` Steven Rostedt
2020-03-05 20:26                         ` Markus Elfring
2020-03-05 20:57                           ` Steven Rostedt
2020-03-05 19:00                   ` Steven Rostedt
2020-03-05 19:14                     ` Markus Elfring
2020-03-05 19:25                       ` Steven Rostedt
2020-03-05 20:10                         ` Markus Elfring
2020-03-05 20:56                           ` Steven Rostedt
2020-03-05 21:26                             ` Markus Elfring [this message]
2020-03-05 10:32     ` [PATCH v5] " Masami Hiramatsu
2020-03-05 13:36     ` [PATCH v5.1] " Masami Hiramatsu
2020-03-05 14:00       ` Markus Elfring
2020-03-06  1:51         ` Masami Hiramatsu
2020-03-06  9:34           ` Markus Elfring
2020-03-06 14:04             ` Masami Hiramatsu
2020-03-06 18:14               ` [v5.1] " Markus Elfring
2020-03-06 18:40               ` Markus Elfring
2020-03-14  8:45       ` [PATCH v5.1] " Markus Elfring
2020-03-05  9:22   ` [PATCH v5] " Markus Elfring
2020-03-05 10:19   ` Markus Elfring
2020-03-05 16:07     ` Randy Dunlap
2020-03-05  9:10 ` [v5 0/1] Documentation: bootconfig: Documentation updates 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=7976cd6c-da28-2df7-492f-7d412e40ff5e@web.de \
    --to=markus.elfring@web.de \
    --cc=corbet@lwn.net \
    --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).