From: Jeff Layton <jlayton@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Justin Stitt <justinstitt@google.com>,
Lorenzo Stoakes <ljs@kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Jori Koolstra <jkoolstra@xs4all.nl>,
Krzysztof Kozlowski <krzk@kernel.org>,
Brian Foster <bfoster@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
David Disseldorp <ddiss@suse.de>,
Mark Brown <broonie@kernel.org>,
Jani Nikula <jani.nikula@intel.com>,
Jens Axboe <axboe@kernel.dk>,
David Hildenbrand <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
"Christian Brauner (Amutable)" <brauner@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Documentation: remove the requirement for LLM attribution
Date: Thu, 02 Jul 2026 11:02:19 -0400 [thread overview]
Message-ID: <8a1cbee162ce85bb34b279de60726bee565d7279.camel@kernel.org> (raw)
In-Reply-To: <20260702145322.GG3534761@killaraus.ideasonboard.com>
On Thu, 2026-07-02 at 17:53 +0300, Laurent Pinchart wrote:
> On Thu, Jul 02, 2026 at 10:32:48AM -0400, Jeff Layton wrote:
> > We've had this requirement in place in the Documentation for several
> > months, but it's becoming clear that the signal to noise ratio from this
> > is quite low.
> >
> > 1/ It's not universally followed. While many people do try to attribute
> > the LLMs in good faith, not everyone does for various reasons.
> >
> > 2/ It basically serves as free advertising for proprietary LLM companies.
> >
> > 3/ It's not clear why we want to collect this info in the first place.
> >
> > Given that the data this provides is flawed at best and is being
> > collected for a purpose that isn't clear, let's just kill the
> > requirement for these tags from the kernel at large.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > Christian had proposed watering down the LLM attribution, but I think
> > it's not productive to try and track this until we have a clearer sense
> > of what we want to do with this information and how to make it more
> > reliable.
> > ---
> > Documentation/process/coding-assistants.rst | 22 ----------------------
> > Documentation/process/submitting-patches.rst | 10 ----------
>
> You're missing scripts/checkpatch.pl.
>
> > 2 files changed, 32 deletions(-)
> >
> > diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst
> > index 899f4459c52d..c4cc0917fc92 100644
> > --- a/Documentation/process/coding-assistants.rst
> > +++ b/Documentation/process/coding-assistants.rst
> > @@ -35,25 +35,3 @@ is responsible for:
> > * Ensuring compliance with licensing requirements
> > * Adding their own Signed-off-by tag to certify the DCO
> > * Taking full responsibility for the contribution
> > -
> > -Attribution
> > -===========
> > -
> > -When AI tools contribute to kernel development, proper attribution
> > -helps track the evolving role of AI in the development process.
> > -Contributions should include an Assisted-by tag in the following format::
> > -
> > - Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]
> > -
> > -Where:
> > -
> > -* ``AGENT_NAME`` is the name of the AI tool or framework
> > -* ``MODEL_VERSION`` is the specific model version used
> > -* ``[TOOL1] [TOOL2]`` are optional specialized analysis tools used
> > - (e.g., coccinelle, sparse, smatch, clang-tidy)
> > -
> > -Basic development tools (git, gcc, make, editors) should not be listed.
> > -
> > -Example::
> > -
> > - Assisted-by: Claude:claude-3-opus coccinelle sparse
>
> Documentation/process/generated-content.rst still clearly requests
> contributors to disclose usage of code-generation tools. Even if we drop
> the Assisted-by tag, I think it is useful to mention the requirement
> here (probably including a link to generated-content.rst).
>
Fair point. Maybe we should keep the Attribution section then, and give
it some brief text like:
"Contributions developed with LLM help should also follow the
guidelines outlined in the generated-content document."
With a link to generated-content.rst?
> > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> > index cc6a1f73d7f2..b74c38aa9770 100644
> > --- a/Documentation/process/submitting-patches.rst
> > +++ b/Documentation/process/submitting-patches.rst
> > @@ -634,16 +634,6 @@ bugzilla.kernel.org is a public place in this sense, but email addresses
> > used there are private; so do not expose them in tags, unless the person
> > used them in earlier contributions.
> >
> > -Using Assisted-by:
> > -------------------
> > -
> > -If you used any sort of advanced coding tool in the creation of your patch,
> > -you need to acknowledge that use by adding an Assisted-by tag. Failure to
> > -do so may impede the acceptance of your work. Please see
> > -Documentation/process/coding-assistants.rst for details regarding the
> > -acknowledgment of coding assistants.
> > -
> > -
> > .. _the_canonical_patch_format:
> >
> > The canonical patch format
> >
> > ---
> > base-commit: 665159e246749578d4e4bfe106ee3b74edcdab18
> > change-id: 20260702-aidoc-7e18f221d63a
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-07-02 15:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 14:32 [PATCH] Documentation: remove the requirement for LLM attribution Jeff Layton
2026-07-02 14:53 ` Laurent Pinchart
2026-07-02 14:58 ` Lorenzo Stoakes
2026-07-02 15:02 ` Jeff Layton [this message]
2026-07-02 15:07 ` Lorenzo Stoakes
2026-07-02 14:57 ` Lorenzo Stoakes
2026-07-02 15:28 ` Laurent Pinchart
2026-07-02 15:36 ` Lorenzo Stoakes
2026-07-02 15:44 ` Laurent Pinchart
2026-07-02 15:07 ` Greg KH
2026-07-02 15:13 ` Jonathan Corbet
2026-07-02 15:20 ` Lorenzo Stoakes
2026-07-02 18:46 ` Andreas Dilger
2026-07-03 2:57 ` Theodore Tso
2026-07-03 11:50 ` Jori Koolstra
2026-07-03 16:12 ` Andreas Dilger
2026-07-02 15:15 ` Lorenzo Stoakes
2026-07-02 15:33 ` Jori Koolstra
2026-07-02 15:37 ` Lorenzo Stoakes
2026-07-02 15:36 ` Laurent Pinchart
2026-07-02 15:57 ` Jeff Layton
2026-07-02 16:13 ` Laurent Pinchart
2026-07-02 16:19 ` Greg KH
2026-07-02 16:32 ` Laurent Pinchart
2026-07-03 6:37 ` Greg KH
2026-07-03 7:23 ` David Hildenbrand (Arm)
2026-07-03 7:30 ` Greg KH
2026-07-03 7:33 ` David Hildenbrand (Arm)
2026-07-03 11:42 ` Theodore Tso
2026-07-03 11:53 ` Laurent Pinchart
2026-07-03 12:04 ` Jori Koolstra
2026-07-02 16:48 ` Jeff Layton
2026-07-02 16:50 ` Lorenzo Stoakes
2026-07-02 21:17 ` Boris Burkov
2026-07-02 23:17 ` SJ Park
2026-07-03 7:05 ` David Hildenbrand (Arm)
2026-07-03 13:12 ` Lorenzo Stoakes
2026-07-03 16:32 ` Laurent Pinchart
2026-07-03 18:22 ` David Hildenbrand (Arm)
2026-07-03 18:26 ` David Hildenbrand (Arm)
2026-07-02 23:05 ` SJ Park
2026-07-02 16:11 ` Chuck Lever
2026-07-02 16:14 ` Lorenzo Stoakes
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=8a1cbee162ce85bb34b279de60726bee565d7279.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=cem@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=ddiss@suse.de \
--cc=hch@infradead.org \
--cc=jani.nikula@intel.com \
--cc=jkoolstra@xs4all.nl \
--cc=justinstitt@google.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@kernel.org \
--cc=workflows@vger.kernel.org \
/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