mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	 Lorenzo Stoakes <ljs@kernel.org>, Boris Burkov <boris@bur.io>,
	 Jeff Layton <jlayton@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	 Jonathan Corbet <corbet@lwn.net>,
	Justin Stitt <justinstitt@google.com>,
	 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>,
	 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: Tue, 07 Jul 2026 20:53:23 +0200	[thread overview]
Message-ID: <20260707-siebzehn-geleast-gastmahl-4889a8f6b474@brauner> (raw)
In-Reply-To: <20260707141803.GA254690@killaraus.ideasonboard.com>

On 2026-07-07 17:18 +0300, Laurent Pinchart wrote:
> On Tue, Jul 07, 2026 at 03:28:49PM +0200, David Hildenbrand (Arm) wrote:
> > On 7/7/26 14:40, Laurent Pinchart wrote:
> > > On Tue, Jul 07, 2026 at 11:49:31AM +0200, David Hildenbrand (Arm) wrote:
> > >> On 7/7/26 11:20, Lorenzo Stoakes wrote:
> > >>>
> > >>> I think the silence suggests nobody :)
> > >>>
> > >>> What we could do is send a patch to simply add a section on adding a comment
> > >>> explaining _what_ used an LLM and strongly suggesting it would be helpful to do
> > >>> so.
> > >>>
> > >>> That should hopefully be uncontroversial, then later (or alongside that?) we
> > >>> could submit an RFC for making the language move to 'you MUST do this', as that
> > >>> will probably be the more controversial bit.
> > >>
> > >> Maybe we should just spell out about which scenario we care about where we really
> > >> expect the disclosure.
> > >>
> > >> Sure, it might be more controversial and we could have that in a separate patch.
> > >>
> > >> I was thinking of the following end result:
> > >>
> > >> diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst
> > >> index 899f4459c52d2..4c2ab4dfc6da7 100644
> > >> --- a/Documentation/process/coding-assistants.rst
> > >> +++ b/Documentation/process/coding-assistants.rst
> > >> @@ -40,20 +40,37 @@ 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::
> > >> +helps track the evolving role of AI in the development process. Further,
> > >> +for reviewers and maintainers it is also crucially important to know how
> > >> +AI tools were used.
> > >>  
> > >> -  Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]
> > >> +Contributions that used AI to generate significant portions of code,
> > >> +comments, or patch descriptions must include an Assisted-by tag in the
> > >> +following format::
> > >>  
> > >> -Where (preferred):
> > >> +  Assisted-by: LLM # brief description of usage
> > >> +
> > >> +Or alternatively::
> > >> +
> > >> +  Assisted-by: AGENT_NAME:MODEL_VERSION # brief description of usage
> > > 
> > > I would like to drop this one. As I understand, several people objected
> > > to including the product name in the git history as it is just free
> > > adverising, and nobody objected to dropping it.
> > 
> > Yeah. I mean, we could go the following direction (dropping the models and
> > encouraging also a description of usage for other tools), but not sure how
> > much pushback we will get:
> 
> I haven't heard anyone involved in this mail thread objecting to the
> concepts you translated into sentences below, so I think it's worth a
> try. Of course there may be objections from people who are not aware of
> this very conversation.

Then someone can basically just merge the original patch I sent since
everyone seems to agree on that front. And then the extension to include
how the LLM was used can be discussed in a separate patch.


  parent reply	other threads:[~2026-07-07 18:53 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 14:32 Jeff Layton
2026-07-02 14:53 ` Laurent Pinchart
2026-07-02 14:58   ` Lorenzo Stoakes
2026-07-02 15:02   ` Jeff Layton
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-06  8:44                   ` Mauro Carvalho Chehab
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-07  9:20                       ` Lorenzo Stoakes
2026-07-07  9:49                         ` David Hildenbrand (Arm)
2026-07-07  9:55                           ` Lorenzo Stoakes
2026-07-07 13:29                             ` David Hildenbrand (Arm)
2026-07-07 15:10                               ` Lorenzo Stoakes
2026-07-07 17:10                                 ` Darrick J. Wong
2026-07-07 18:16                                   ` Lorenzo Stoakes
2026-07-07 10:01                           ` Geert Uytterhoeven
2026-07-07 13:31                             ` David Hildenbrand (Arm)
2026-07-07 12:40                           ` Laurent Pinchart
2026-07-07 13:28                             ` David Hildenbrand (Arm)
2026-07-07 14:18                               ` Laurent Pinchart
2026-07-07 14:59                                 ` Lorenzo Stoakes
2026-07-07 15:05                                   ` Laurent Pinchart
2026-07-07 18:53                                 ` Christian Brauner [this message]
2026-07-07 18:55                                   ` Christian Brauner
2026-07-07 19:03                                     ` Jonathan Corbet
2026-07-07 19:06                                       ` Lorenzo Stoakes
2026-07-07 10:15                         ` Jori Koolstra
2026-07-07 10:20                           ` Lorenzo Stoakes
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=20260707-siebzehn-geleast-gastmahl-4889a8f6b474@brauner \
    --to=brauner@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=boris@bur.io \
    --cc=broonie@kernel.org \
    --cc=cem@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=ddiss@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jani.nikula@intel.com \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --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