linux-kernel - Re: [v5] Documentation: bootconfig: Update boot configuration documentation

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a6a216ce-8e41-ca35-bd65-25bcacde1d28@infradead.org>
Date:   Thu, 5 Mar 2020 10:57:20 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Markus Elfring <Markus.Elfring@....de>, linux-doc@...r.kernel.org
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: [v5] Documentation: bootconfig: Update boot configuration
 documentation

On 3/5/20 10:43 AM, Markus Elfring wrote:
>>>> If you would (could) be more concrete (or discrete) in your suggestions,
>>>> I would be glad to comment on them.
>>>
>>> Does this view indicate any communication difficulties?
>>
>> Probably.
>>
>>> Which of the possibly unanswered issues do you find not concrete enough so far?
>>
>> e.g.:
>>>>>  Will the clarification become more constructive for remaining challenges?
> 
> Do you expect that known open issues need to be repeated for each patch revision?

Ideally not, but not very much is ideal.

IOW, it is sometimes required (if one cares enough; sometimes
one just gives up).

> How do you think about the desired tracking of bug reports
> also for this software?

I expect that more users will begin to use it and report problems
as they see fit.  They can use mailing list(s) and/or
bugzilla.kernel.org.  I'm not terribly concerned about it.
Masami seems to be responsive.

thanks.
-- 
~Randy