Re: [PATCH] [v3] Documentation: Provide guidelines for tool-generated content

Steven Rostedt <[email protected]>
Newsgroups dev.linux.lists.ksummit,org.kernel.vger.workflows
Message-ID <[email protected]>
On Fri, 14 Nov 2025 10:35:28 -0800
Dave Hansen <[email protected]> wrote:

> 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 in
> 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.

Thanks Dave for pushing this through!

Reviewed-by: Steven Rostedt <[email protected]>

-- Steve

> 
> Signed-off-by: Dave Hansen <[email protected]>
> Reviewed-by: Shuah Khan <[email protected]>
> Reviewed-by: Kees Cook <[email protected]>
> Reviewed-by: Greg Kroah-Hartman <[email protected]>
> Reviewed-by: Miguel Ojeda <[email protected]>
> Cc: NeilBrown <[email protected]>
> Cc: Lorenzo Stoakes <[email protected]>
> Cc: Dan Williams <[email protected]>
> Cc: Theodore Ts'o <[email protected]>
> Cc: Sasha Levin <[email protected]>
> Cc: Jonathan Corbet <[email protected]>
> Cc: Vlastimil Babka <[email protected]>
> Cc: [email protected]
> Cc: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.