public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Kees Cook <kees@kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] [v2] Documentation: Provide guidelines for tool-generated content
Date: Fri, 7 Nov 2025 17:47:10 +0900	[thread overview]
Message-ID: <2025110753-affront-antarctic-8695@gregkh> (raw)
In-Reply-To: <20251105231514.3167738-1-dave.hansen@linux.intel.com>

On Wed, Nov 05, 2025 at 03:15:14PM -0800, Dave Hansen 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.
> 
> The shiny new AI tools (chatbots, coding assistants and more) are
> impressive.  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.
> 
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Cc: Sasha Levin <sashal@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Kees Cook <kees@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Miguel Ojeda <ojeda@kernel.org>
> Cc: Shuah Khan <shuah@kernel.org>
> 

Looks good, thanks for doing this:

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  parent reply	other threads:[~2025-11-07  8:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 23:15 [PATCH] [v2] Documentation: Provide guidelines for tool-generated content Dave Hansen
2025-11-06 22:42 ` Shuah
2025-11-06 22:49   ` Dave Hansen
2025-11-07  3:40 ` Kees Cook
2025-11-07  8:47 ` Greg Kroah-Hartman [this message]
2025-11-07 10:58 ` Bagas Sanjaya
2025-11-08  0:11 ` dan.j.williams
2025-11-13 22:17   ` Dave Hansen
2025-11-08  1:52 ` Miguel Ojeda
2025-11-13 22:21   ` Dave Hansen
2025-11-10  7:43 ` Vlastimil Babka
2025-11-10  8:58   ` Christian Brauner
2025-11-10 16:08     ` Dave Hansen
2025-11-10 17:25     ` Laurent Pinchart
2025-11-10 17:41       ` Dave Hansen
2025-11-10 17:44       ` Linus Torvalds
2025-11-10 17:56         ` Luck, Tony
2025-11-10 18:39         ` Mike Rapoport
2025-11-10 19:05           ` Linus Torvalds
2025-11-10 19:18             ` H. Peter Anvin
2025-11-10 19:36               ` Linus Torvalds
2025-11-10 19:54                 ` Steven Rostedt
2025-11-10 20:00                   ` Konstantin Ryabitsev
2025-11-10 20:25                     ` Steven Rostedt
2025-11-10 21:21                   ` James Bottomley
2025-11-10 21:42                     ` Steven Rostedt
2025-11-10 21:52                       ` Luck, Tony
2025-11-10 22:07                         ` James Bottomley
2025-11-10 23:16                   ` Theodore Ts'o
2025-11-11  9:35                 ` Lorenzo Stoakes
2025-11-11 13:08                   ` Theodore Ts'o
2025-11-10 17:46       ` Steven Rostedt
2025-11-10 10:48 ` Lorenzo Stoakes
2025-11-10 11:15   ` Lorenzo Stoakes
2025-11-10 15:19   ` Jonathan Corbet
2025-11-10 15:30     ` Lorenzo Stoakes
2025-11-10 15:44       ` Jonathan Corbet
2025-11-10 16:35   ` Dave Hansen
2025-11-10 16:51     ` Lorenzo Stoakes
2025-11-10 18:29   ` Steven Rostedt
2025-11-11 23:45 ` NeilBrown
2025-11-14  1:09   ` Dave Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025110753-affront-antarctic-8695@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox