From: "Theodore Tso" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Layton <jlayton@kernel.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>,
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 07:42:35 -0400 [thread overview]
Message-ID: <akeaouJETPWpE838@mit.edu> (raw)
In-Reply-To: <2026070343-copied-quarters-1e2a@gregkh>
On Fri, Jul 03, 2026 at 09:30:28AM -0500, Greg KH wrote:
> > So clarifying there that a "Assisted-by: LLM" is also good enough would make
> > sense if we agree on that.
>
> If we all agree on that, I'm saying that _I_ don't care, but others
> might.
I agree that requiring the model name is not a good idea, because some
developers might be using unreleased products where the name itself
might not be public. So allowing the version number of the LLM to be
elided would be a good change.
I'll also note that it's starting to be the case where tool is
actually quite relevant. So it's not just about the LLM Model, but
whether you're using Codex, Claude Code, OpenCode, or Shahiko. You
can use the tool or the harness with different models.
So whether the tag is:
Assisted-By: OpenCode:Gemini 3.5 Pro
Assisted-By: Claude Code
Assisted-By: LLM
I'd be fine with reviewing patches with any of the above. However, to
me that's actually not the most interesting part. See below....
> For me, the info after "Assisted-by:" doesn't matter, it's the first
> part.
For me, what I care most about is *how* the LLM was used. For
example, if someone just used the output of Sashiko to fix a problem
in their commit, that's one kind of "Assisted-by". If Sahsiko
identifies a pre-existing bug, and the developer addes a patch to the
patch series, or creates a new patch series, that's a different kind
of "Assisted-by". A third kind of "Assisted-by" might include asking
the LLM to create a Coccinelle semantic patches (because I'm not smart
enough to create semantic patches).
And of course, all of this is quite different from the stereotypical
"vibe coding" where the LLM generates thousands of lines of code which
the human doesn't understand before sending the pull request. :-)
So for me, adding something after a #-sign comment explaning how the
LLM was used would be very useful.
> > My kids should clean up their room; doesn't work.
>
> But, if you notice that your kids didn't clean up their room, and you
> had told them to, you can then talk to them about doing it properly
> based on what they are supposed to be doing.
Another metaphor might be that people shouldn't try to evade paying
their taxes; merely passing a law saying they have to file correct tax
returns doesn't guarantee this. But it was specifically the law
against tax evasion is how US Law Enforcement arrested the Chicago mob
boss Al Capone.
Just because some people might lie doesn't mean that we shouldn't
bother to ask everyone to fill out tax returns.
Cheers,
- Ted
next prev parent reply other threads:[~2026-07-03 11:43 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 [this message]
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=akeaouJETPWpE838@mit.edu \
--to=tytso@mit.edu \
--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=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