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: <20260123103040.7752d6c1@gandalf.local.home>
Date: Fri, 23 Jan 2026 10:30:40 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Dave Hansen <dave.hansen@...ux.intel.com>
Cc: 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>, Dan Williams <dan.j.williams@...el.com>, "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>, Jonathan Corbet <corbet@....net>, Vlastimil Babka
 <vbabka@...e.cz>, workflows@...r.kernel.org, ksummit@...ts.linux.dev
Subject: Re: [PATCH] [v6] Documentation: Provide guidelines for
 tool-generated content

On Mon, 19 Jan 2026 12:04:18 -0800
Dave Hansen <dave.hansen@...ux.intel.com> wrote:

I decided to go over it one last time.
> +
> +Out of Scope
> +============
> +
> +These guidelines do not apply to tools that make trivial tweaks to
> +preexisting content. Nor do they pertain to tooling that helps with
> +menial tasks. Some examples:
> +
> + - Spelling and grammar fix ups, like rephrasing to imperative voice
> + - Typing aids like identifier completion, common boilerplate or
> +   trivial pattern completion
> + - Purely mechanical transformations like variable renaming
> + - Reformatting, like running Lindent, ``clang-format`` or
> +   ``rust-fmt``
> +
> +Even whenever your tool use is out of scope, you should still always

Somehow the above reads really weird to me. "Even whenever your tool use is
out of scope". Do you mean "Even when your tool use is out of scope" ?

> +consider if it would help reviewing your contribution if the reviewer
> +knows about the tool that you used.
> +

Other than that, LGTM!

Thanks,

-- Steve