Linux Documentation
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>, Jens Axboe <axboe@kernel.dk>,
	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,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Thu, 2 Jul 2026 16:47:18 +0300	[thread overview]
Message-ID: <20260702134718.GF3534761@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260702-weitreichend-aufgearbeitet-flausen-fd92f38bbba0@brauner>

On Thu, Jul 02, 2026 at 03:26:58PM +0200, Christian Brauner wrote:
> On Thu, Jul 02, 2026 at 01:51:10PM +0200, David Hildenbrand (Arm) wrote:
> > On 7/2/26 12:04, Lorenzo Stoakes wrote:
> > > (thanks for the cc-!)
> > > 
> > > On Thu, Jul 02, 2026 at 09:46:37AM +0200, David Hildenbrand (Arm) wrote:
> > >> On 7/2/26 09:27, Christian Brauner wrote:
> > >>>
> > >>> I think we should just drop any attribution as a general kernel-wide
> > >>> rule and let subsystems require them as needed. Then you can have all
> > >>> the complexity in mm for this that you think is needed for your
> > >>> workflow to function. This is precisely what the subsystem profiles are
> > >>> for. So maybe just add:
> > > 
> > > A single comment is complexity?
> > 
> > I think Christian meant more elaborate rules. More than just "If you used LLMs,
> > disclose how you used them."
> 
> Yes.
> 
> I'm going to follow netdev and start dropping those tags from the
> changelog completely too. After speaking to some bpf maintainers they
> also don't use the tag. So I can safely assume that 3 large subsystems
> don't bother with it.
> 
> So seems to me that such requirements should just move into the
> subsystem profiles.
> 
> I think as a global policy this has ran its course.
> 
> > > And is it really that egregious to include a tag? You can ignore it if you don't
> > > care.
> > 
> > I hate the current tags as they are. The question I am asking myself: assume we
> > stop using the Assisted-by for LLM stuff. What to do with the other tools? Why
> > are LLMs suddenly no longer a tool to mention there.
> 
> Tbh, I think that's equally pointless. There are also very few instances
> of non-AI attribution with Assisted-by.
> 
> If the tool mattered to what was done significantly then it should just
> be disclosed in an appropriate paragraph in the commit message. The tag
> itself is imho equally useless for this. I really don't need to know
> that you used grep or git-sed or tcpdump and it certainly doesn't need
> to spam the trailers.

We've dealt with coccinelle-generated code changes for ages without
Assisted-by tags and without any issue. Submitters typically include the
semantic patch in the commit message, or just mentioned coccinelle was
used. I personally feel that the apparent generic scope of the
Assisted-by trailer tag, and the fact that this is documented in a file
named generated-content.rst, is an attempt to pretend generative AI is
"just another tool" comparable to coccinelle or checkpatch.

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2026-07-02 13:47 UTC|newest]

Thread overview: 56+ 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
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 [this message]
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

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=20260702134718.GF3534761@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ast@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --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=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