linux-kernel - Re: [PATCH] [v5] Documentation: Provide guidelines for tool-generated content

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] [day] [month] [year] [list]

Message-ID: <3ad94715-8645-4520-83fc-b3bf18c472cd@intel.com>
Date: Mon, 19 Jan 2026 11:57:28 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jonathan Corbet <corbet@....net>,
 Dave Hansen <dave.hansen@...ux.intel.com>, linux-kernel@...r.kernel.org
Cc: Shuah Khan <shuah@...nel.org>, Kees Cook <kees@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Miguel Ojeda <ojeda@...nel.org>, Luis Chamberlain <mcgrof@...nel.org>,
 SeongJae Park <sj@...nel.org>, Dan Williams <dan.j.williams@...el.com>,
 Steven Rostedt <rostedt@...dmis.org>, "Paul E . McKenney"
 <paulmck@...nel.org>, Simon Glass <simon.glass@...onical.com>,
 NeilBrown <neilb@...mail.net>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 Theodore Ts'o <tytso@....edu>, Sasha Levin <sashal@...nel.org>,
 Vlastimil Babka <vbabka@...e.cz>, workflows@...r.kernel.org,
 ksummit@...ts.linux.dev
Subject: Re: [PATCH] [v5] Documentation: Provide guidelines for tool-generated
 content

On 1/13/26 11:22, Jonathan Corbet wrote:
>> --- a/Documentation/process/index.rst
>> +++ b/Documentation/process/index.rst
>> @@ -68,6 +68,7 @@ beyond).
>>     stable-kernel-rules
>>     management-style
>>     researcher-guidelines
>> +   generated-content
> At some point, $SOMEBODY should probably add a brief reference to
> submitting-patches.rst as well.

I can definitely send a follow-up for that.

It has a "Tooling" section. But it also seems like a sentence at the
top, like:

...
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -15,6 +15,8 @@ Documentation/process/submit-checklist.rst
 for a list of items to check before submitting code.
 For device tree binding patches, read
 Documentation/devicetree/bindings/submitting-patches.rst.
+If you used tools to generate part of your contribution, read
+Documentation/process/generated-content.rst.

 This documentation assumes that you're using ``git`` to prepare your patches.
 If you're unfamiliar with ``git``, you would be well-advised to learn how to

might also be appropriate.

Any preferences?