linux-kernel - Re: [PATCH] [v6] 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: <87cy34hrs3.fsf@trenco.lwn.net>
Date: Tue, 20 Jan 2026 14:56:44 -0700
From: Jonathan Corbet <corbet@....net>
To: Dave Hansen <dave.hansen@...ux.intel.com>, linux-kernel@...r.kernel.org
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, 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>, Lee Jones <lee@...nel.org>, Lorenzo Stoakes
 <lorenzo.stoakes@...cle.com>, NeilBrown <neilb@...mail.net>, 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] [v6] Documentation: Provide guidelines for
 tool-generated content

Dave Hansen <dave.hansen@...ux.intel.com> writes:

> In the last few years, the capabilities of coding tools have exploded.
> As those capabilities have expanded, contributors and maintainers have
> more and more questions about how and when to apply those
> capabilities.
>
> Add new Documentation to guide contributors on how to best use kernel
> development tools, new and old.
>
> Note, though, there are fundamentally no new or unique rules in this
> new document. It clarifies expectations that the kernel community has
> had for many years. For example, researchers are already asked to
> disclose the tools they use to find issues by
> Documentation/process/researcher-guidelines.rst. This new document
> just reiterates existing best practices for development tooling.
>
> In short: Please show your work and make sure your contribution is
> easy to review.
>
> Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>

OK, it seems this is ready, so I've just applied it, thanks.

jon