All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>,
	Lorenzo Stoakes <ljs@kernel.org>,
	 "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
	Linus Torvalds	 <torvalds@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>, Jens Axboe	 <axboe@kernel.dk>,
	Vlastimil Babka <vbabka@kernel.org>,
	 workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Thu, 02 Jul 2026 09:48:36 -0400	[thread overview]
Message-ID: <28cce41770aa3d2b3eba56f6c15bae790e757285.camel@kernel.org> (raw)
In-Reply-To: <8aa9788c9fc0fc02e2493b3f910437d613506125@intel.com>

On Thu, 2026-07-02 at 16:41 +0300, Jani Nikula wrote:
> On Thu, 02 Jul 2026, Lorenzo Stoakes <ljs@kernel.org> wrote:
> > "Say how much of your patch is LLM written, here are some examples".
> 
> I think the question is, did you offload understanding to the LLM, or
> just the creation of the patch.
> 
> I think Assisted-by gets used as an indication of "the contributor might
> not understand the contribution", and the patch might warrant extra
> scrutiny. But that's not reliable by any means.
> 
> Right or wrong, it used to be that the lack of polish in a patch was
> used as a poor proxy for that, but now we get polished patches from
> LLMs.
> 

Exactly.

I think trying gatekeep patches based on whether they were LLM
generated is a long-term losing battle. I prefer to focus on the value
of the patches themselves and not get too wrapped up in how they were
created.

The original focus of this discussion was around Assisted-by: tags
though. I'd like to circle back to that:

Do we have enough consensus to drop the requirement for them? The
patches that are most problematic are pretty universally unattributed
anyway.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-07-02 13:48 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
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 [this message]
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=28cce41770aa3d2b3eba56f6c15bae790e757285.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=jani.nikula@intel.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 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.