From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>,
Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>, Jens Axboe <axboe@kernel.dk>,
David Hildenbrand <david@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Lorenzo Stoakes <ljs@kernel.org>
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Thu, 2 Jul 2026 10:44:34 +0200 [thread overview]
Message-ID: <a17b9a17-0ca7-4912-836d-4637cd0110f7@kernel.org> (raw)
In-Reply-To: <akYasD1ckWcH1C0g@lt-jori.localdomain>
On 7/2/26 10:12, Jori Koolstra wrote:
> Ah, I still reigniting this discussion again :)
>
> What about a combination of what David and Jeff say? The whole point
> seems to me that the salient information is not that an LLM was used (or
> are we going to tag Sashiko as well or any other LLM-based code review
> tool?), but what is was used to do. This information may be relevant for
> how the review is approached. The latter should perhaps only be in the
> cover letter and then we can drop the assisted-by tags altogether.
>
> The question about enforcement remains.
It's not possible to enforce it. People can deny it if the tag is missing
and you confront them and even though the submission has many signs of being
obviously LLM, there is no definite proof. We've seen (likely, as there's no
proof!) that happen in mm.
Such situation then penalizes those who disclose so obviously they won't. We
should drop the tag and instead think how we can empower maintainers to be
able to use their own judgment and deprioritize dealing with what they
perceive as LLM slop, without fearing consequences of not being properly
responsible etc, and not rely on any non-enforceable tags for that.
next prev parent reply other threads:[~2026-07-02 8:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:54 [PATCH RFC] coding-assistants: simplify attribution Christian Brauner
2026-07-01 16:08 ` Mark Brown
2026-07-02 7:10 ` Christian Brauner
2026-07-01 16:08 ` Jonathan Corbet
2026-07-01 16:12 ` David Hildenbrand (Arm)
2026-07-02 7:11 ` Christian Brauner
2026-07-02 9:51 ` David Disseldorp
2026-07-01 16:10 ` David Hildenbrand (Arm)
2026-07-02 7:27 ` Christian Brauner
2026-07-02 7:46 ` David Hildenbrand (Arm)
2026-07-02 8:10 ` Laurent Pinchart
2026-07-02 8:16 ` David Hildenbrand (Arm)
2026-07-02 10:04 ` Lorenzo Stoakes
2026-07-02 8:08 ` Laurent Pinchart
2026-07-02 8:28 ` Christian Brauner
2026-07-02 9:24 ` Lorenzo Stoakes
2026-07-01 18:35 ` Jeff Layton
2026-07-01 18:53 ` Jakub Kicinski
2026-07-02 7:29 ` Christian Brauner
2026-07-02 7:28 ` Christian Brauner
2026-07-02 8:12 ` Jori Koolstra
2026-07-02 8:44 ` Vlastimil Babka (SUSE) [this message]
2026-07-02 9:09 ` Jori Koolstra
2026-07-02 9:39 ` Lorenzo Stoakes
2026-07-02 9:37 ` Lorenzo Stoakes
2026-07-02 9:38 ` Laurent Pinchart
2026-07-02 9:44 ` Lorenzo Stoakes
2026-07-02 10:34 ` Krzysztof Kozlowski
2026-07-02 10:27 ` Krzysztof Kozlowski
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=a17b9a17-0ca7-4912-836d-4637cd0110f7@kernel.org \
--to=vbabka@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=jlayton@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=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