From: Jonathan Corbet <corbet@lwn.net>
To: Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>,
David Hildenbrand <david@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Christian Brauner (Amutable)" <brauner@kernel.org>
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Wed, 01 Jul 2026 10:08:11 -0600 [thread overview]
Message-ID: <87jyreofpw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260701-work-coding-assistants-v1-1-a20a94d1d606@kernel.org>
Christian Brauner <brauner@kernel.org> writes:
> I remain very confused by our coding assistant contribution guidelines.
> I'm going to be a bit polemic now but this seriously in good faith.
>
> Why precisely do we require all this detailed information about what
> specific coding assistant was used?
From my memory of the discussions:
- If a specific LLM turns out to be in a bad position with regard to
some copyright ruling, we can identify the commits that might have
been tainted by it.
- Similarly should an LLM prove to have an inclination toward specific
types of security issues.
Whether either of these would ever actually prove useful is not
something I can hazard a guess for.
> I find it very irritating that our git history has effectively started
> to function a bit like a free advertising platform for a bunch of AI
> companies and their proprietary agents and models.
>
> And it reamins unclear to me what exactly we do get out of this detailed
> information: Do we want to run statistical analysis on what agent and
> model is used the most and publish that on LWN at some point?
...wasn't in my plans ...
> I acknowledge that my stance is even more radical: imho we would just
> stop it with any disclosure requirements completely. It's useless imho.
> We already see that other than core contributors most people don't care
> and will just not disclose their usage of AI.
The widespread ignoring of the disclosure rule is, IMO, something we
need to address somehow; were I still on the TAB, I'd be raising the
issue there. Either we find a way to be serious about enforcing the
disclosure rule, or we should just drop it. A rule that everybody
ignores is less than useful.
(That said, 706 commits in 7.2-rc1 include Assisted-by tags, so *some*
people are complying. That's about 5% of the total. What do we think
is the actual use of LLMs for the creation of kernel patches?)
jon
next prev parent reply other threads:[~2026-07-01 16:08 UTC|newest]
Thread overview: 58+ 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-02 11:35 ` Mark Brown
2026-07-01 16:08 ` Jonathan Corbet [this message]
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 11:51 ` David Hildenbrand (Arm)
2026-07-02 12:49 ` Lorenzo Stoakes
2026-07-02 13:41 ` Jani Nikula
2026-07-02 13:48 ` Jeff Layton
2026-07-02 13:26 ` Christian Brauner
2026-07-02 13:35 ` Christoph Hellwig
2026-07-02 13:47 ` Laurent Pinchart
2026-07-02 13:57 ` Lorenzo Stoakes
2026-07-02 14:09 ` Christian Brauner
2026-07-02 14:46 ` Lorenzo Stoakes
2026-07-02 16:18 ` Christian Brauner
2026-07-02 16:29 ` Lorenzo Stoakes
2026-07-02 8:08 ` Laurent Pinchart
2026-07-02 8:28 ` Christian Brauner
2026-07-02 13:48 ` Carlos Maiolino
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)
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 11:57 ` Brian Foster
2026-07-02 12:18 ` Lorenzo Stoakes
2026-07-02 13:07 ` Laurent Pinchart
2026-07-02 13:37 ` Lorenzo Stoakes
2026-07-02 13:47 ` Jori Koolstra
2026-07-02 13:09 ` Brian Foster
2026-07-02 13:25 ` Lorenzo Stoakes
2026-07-02 10:34 ` Krzysztof Kozlowski
2026-07-02 12:23 ` Lorenzo Stoakes
2026-07-02 12:39 ` Krzysztof Kozlowski
2026-07-02 12:53 ` Lorenzo Stoakes
2026-07-02 13:23 ` Laurent Pinchart
2026-07-02 10:27 ` Krzysztof Kozlowski
2026-07-02 11:27 ` Christoph Hellwig
2026-07-02 13:40 ` Carlos Maiolino
2026-07-03 9:21 ` Ellie
2026-07-03 11:58 ` Laurent Pinchart
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=87jyreofpw.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.