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

Message-ID: <69669404e2bf_875d10028@dwillia2-mobl4.notmuch>
Date: Tue, 13 Jan 2026 10:50:44 -0800
From: <dan.j.williams@...el.com>
To: Sasha Levin <sashal@...nel.org>, <dan.j.williams@...el.com>
CC: Dan Carpenter <dan.carpenter@...aro.org>, Dave Hansen
	<dave.hansen@...ux.intel.com>, <linux-kernel@...r.kernel.org>, 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>, "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>,
	Jonathan Corbet <corbet@....net>, Vlastimil Babka <vbabka@...e.cz>,
	<workflows@...r.kernel.org>, <ksummit@...ts.linux.dev>
Subject: Re: [PATCH] [v5] Documentation: Provide guidelines for tool-generated
 content

Sasha Levin wrote:
[..]
> With a rule like the above, 1700+ contributors would have not been able to send
> their patch in.

Good point, I am not suggesting a Reviewed-by hurdle, but can see it
reading that way. I expect that there will always be a significant class
of contributions that will never need author trust to be accepted. Yes,
would need to be careful not to destroy that wellspring of new
contributors.