Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@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: Fri, 3 Jul 2026 19:32:51 +0300	[thread overview]
Message-ID: <20260703163251.GB3734786@killaraus.ideasonboard.com> (raw)
In-Reply-To: <akez23ZhLRSGMFQ1@lucifer>

On Fri, Jul 03, 2026 at 02:12:40PM +0100, Lorenzo Stoakes wrote:
> On Fri, Jul 03, 2026 at 09:05:58AM +0200, David Hildenbrand (Arm) wrote:
> > On 7/2/26 23:17, Boris Burkov wrote:
> > > On Thu, Jul 02, 2026 at 05:50:15PM +0100, Lorenzo Stoakes wrote:
> > >> On Thu, Jul 02, 2026 at 12:48:22PM -0400, Jeff Layton wrote:
> > >>>
> > >>> Do we need a tag for this though?
> > >>>
> > >>> This seems like the kind of information that we would always require in
> > >>> the cover letter of a series (or the little place in an individual
> > >>> patch for comments that don't get merged). That would also allow you to
> > >>> convey a lot more nuance about how it was used.
> > >>>
> > >>> ISTM asking people to disclose LLM usage in a cover letter would give
> > >>> everyone what they want: Information about whether and possibly how an
> > >>> LLM was used, and it also wouldn't clutter up the changelogs with these
> > >>> tags.
> > >>
> > >> It's much much clearer and easier to just have a standardised tag for that.
> > >>
> > >> You can see that (and grep for that) immediately, vague paragraphs not so much.
> > >>
> > >
> > > At the risk of being pedantic on a point where I think the document is
> > > kind of lacking:
> > >
> > > What level of assistance crosses the bar for an "Assisted-by: LLM" tag?
> > >
> > > Some sample levels of assistance to illustrate the point:
> > >
> > > 1. I used an llm to one-shot vibe-code a patch
> > > 2. I used an llm to write a patch but carefully reviewed every line
> > > 3. I used an llm to explore the design space for a patch but wrote it
> > > manually
> > > 4. I used an llm to debug or reproduce a kernel issue but then wrote the
> > > fix manually after fully understanding the defect
> > > 5. I used an llm to review a patch I wrote
> > > 6. I used an llm to research some chunk of code while writing a patch
> > > 7. I used Google while writing a patch and learned something valuable
> > > from the AI overview at the top
> > >
> > > I personally would 100% use the tag for 1 or 2, and have already done
> > > so. I have not been doing it for 3-5, as I think that will basically
> > > make every patch llm-assisted to the point of the distinction being
> > > meaningless. If we should be doing it for 3-5 (or some subset thereof)
> > > then my mistake and I will certainly start doing so. I would hope most
> > > people agree 6-7 and similar need no tag.
> 
> I personally think 1-2 are the only relevant cases.
> 
> > >
> > > Similar questions abound if you use an llm to help with writing the
> > > English text in the patch or emails.
> > >
> > > I have a feeling that this ambiguity is part of the reason we aren't all
> > > agreeing on the value of the tag?
> >
> > Yes, I raised something similar as reply to Christian's RFC [1], where I said
> > that for me the information *how* it was used is much more important:
> >
> > "
> > Assisted-by: LLM # translate commit message
> > Assisted-by: LLM # generate some test cases
> > Assisted-by: LLM # cleanup logic
> > Assisted-by: LLM # everything and I have no clue what any in here does
> > "
> 
> Yup, and we don't need complicated rules for that just 'document what you used
> it for and give a sense of how much'.
> 
> It's fuzzy but useful.
> 
> >
> > That tag is it stands is pretty useless, really.
> 
> Not to go over it all again but I disagree, even as it stands, it allows us to
> engage in conversation about the LLM usage if admitted, and to point those who
> are misbehaving at the rules if not.
> 
> And it is a clear way to get the boolean 'is this person saying they used an
> LLM'.
> 
> But I agree with you it'd be MUCH more useful if we did the above.
> 
> I wonder if we could get consensus on adding a section to the doc saying that
> it'd be _useful_ to add a comment explaining _what_ you did, and explaining the
> concept with some examples?

I'd support a patch that replaces

Assisted-by: Claude:claude-3-opus coccinelle sparse

with

Assisted-by: LLM # generate some test cases

and rewrites the Attribution section of
Documentation/process/coding-assistants.rst accordingly.

I think most people in this mail thread have expressed that how
generative AI was used is the most important information, and several
people (including myself) have expressed a desire to stop the free
advertising. Unless I missed something, I don't think anyone has
expressed an interest in keeping the agent name and model.

> I can't imagine anybody would disagree with that, and that would get us positive
> forward progress.
> 
> Then later we could debate the details further?
> 
> > I assume most people only really use it for something in-between 1 and 2, but
> > *who knows*.
> >
> > [1] https://lore.kernel.org/r/5e7b9d23-4291-48fb-bdc6-47db82d33c80@kernel.org

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-07-03 16:32 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
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 [this message]
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=20260703163251.GB3734786@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=axboe@kernel.dk \
    --cc=bfoster@redhat.com \
    --cc=boris@bur.io \
    --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=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=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