All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Lorenzo Stoakes <ljs@kernel.org>, Kees Cook <kees@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Sasha Levin <sashal@kernel.org>,
	corbet@lwn.net, skhan@linuxfoundation.org,
	federico.vaga@vaga.pv.it, apw@canonical.com, joe@perches.com,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: remove Assisted-by reference
Date: Tue, 13 Oct 2026 15:55:59 +0200	[thread overview]
Message-ID: <20261013135559.GA161185@killaraus.ideasonboard.com> (raw)
In-Reply-To: <28216768.791900.1791897606751@kpc.webmail.kpnmail.nl>

On Tue, Oct 13, 2026 at 03:20:06PM +0200, Jori Koolstra wrote:
> Op 13-10-2026 15:10 CEST schreef Laurent Pinchart:
> > On Tue, Oct 13, 2026 at 03:03:08PM +0200, Jori Koolstra wrote:
> > > > Op 13-10-2026 14:55 CEST schreef Laurent Pinchart:
> > > > On Tue, Oct 13, 2026 at 02:28:43PM +0200, Jori Koolstra wrote:
> > > > > On Tue, Oct 13, 2026 at 01:25:59AM -0700, Kees Cook wrote:
> > > > > > On Mon, Oct 12, 2026 at 10:56:59PM -0700, Randy Dunlap wrote:
> > > > > > > On 10/12/26 9:24 PM, Kees Cook wrote:
> > > > > > > > On Fri, Oct 09, 2026 at 04:31:37AM -0400, Sasha Levin wrote:
> > > > > > > >> The Maintainers Summit reached consensus to deprecate the Assisted-by
> > > > > > > >> tag. Remove the documentation requiring it.
> > > > > > > >>
> > > > > > > >> Signed-off-by: Sasha Levin <sashal@kernel.org>
> > > > > > > > 
> > > > > > > > Yup, it has become as redundant as specifying what editor I use. ;)
> > > > > > > > 
> > > > > > > > Reviewed-by: Kees Cook <kees@kernel.org>
> > > > > > > 
> > > > > > > and for those of us who don't know details about the discussion,
> > > > > > > how is it redundant?
> > > > > > 
> > > > > > No, I mean I use an LLM constantly for almost all aspects of my
> > > > > > development work, in multiple dimensions, so if the old tag requirement
> > > > > > held, my email body template would just put "Assisted-by: LLM" in there
> > > > > > because at the very least, it drove the build and test stage. It was
> > > > > > redundant in the sense of "yeah, of course I used an LLM at some point
> > > > > > for this patch". ("This tag means nothing *from* me")
> > > > > > 
> > > > > > > Do you assume that everyone now uses it (LLM), just as everyone
> > > > > > > uses an editor?
> > > > > > 
> > > > > > I don't make that assumption, but I always held the position that the
> > > > > > tag was meaningless because it's the human wielding it that matters:
> > > > > > they either sent a good patch or a bad patch, and if it was mangled by
> > > > > > gmail or an LLM, it doesn't really matter. ("This tag means nothing *to*
> > > > > > me")
> > > > > 
> > > > > I think the tag did have a genuine purpose for a while. Now we have just
> > > > > decided to implicitly attach it to every new submitter (because
> > > > > basically that is the case.) The point was that a patch that was
> > > > > obviously LLM generated could be rejected for not carrying the tag, and
> > > > > a patch that carried the tag could be asked to explain further (if they
> > > > > had not done so.) Or at least, that is how I felt and have understood
> > > > > Greg, for instance :)
> > > > > 
> > > > > Essentially, the way I read it, is that Linus said we don't need this
> > > > > roundabout way because we can just reject effortless LLM generated
> > > > > patches outright. This is good and an improvement.
> > > > 
> > > > The absence of the tag on a suspicious series offered a low-effort way
> > > > for maintainers to push back. What's the proposed low-effort replacement
> > > > ?
> > > 
> > > To ignore it, really. Even less effort :)
> > 
> > Are you saying that we should ignore series when we have even a slight
> > suspicion they're not perfect ? If not, I don't understand what you're
> > proposing exactly.
> 
> I am saying it is up to the maintainer.

That has always been the case. It may have been voiced again in a way
that is more noticeable to some, but maintainers have always been in
charge of deciding that they accept.

And at the same time it has never been the case. Maintainers can be
overruled. One of the most recent examples to have made the news was the
merge of rust bindings for the DMA mapping API.

If the situation hasn't fundamentally changed, I hope I'm misreading
this mail thread. I see people who seem to rejoiced at the news they
have gained a power in their fiefdom that they can use and abuse at
will. Being on the receiving end of patches I wish I would have never
received I sympathize and understand we need to adjust processes. On the
flip side, I hope I won't see a patch being rejected on the grounds that
the submitter hasn't attended the same boys' club as the maintainer.

Sanity often prevails after people cool down, I assume that will be the
case here too.

> The word is out and we are allowed to
> ignore poor contributions, in particular if they are LLM generated. The whole point
> is that in the past poor contributions were still a signal someone was trying and
> it might be worthwhile to help them to grow. It is not that signal anymore per se.
> We need other avenues to identify talent. The kernel mentorship program is one of
> those, as is showing up in person at conferences.

I think mailing lists are still a proper avenue. LLM-generated series
(so far) never made me think there was someone trying and interesting in
growing.

> The tag helped some maintainers to push back (like Lorenzo). The tag isn't needed
> anymore, because the push back isn't needed. I think that's an improvement, and at
> any rate was inevitable.

Ignoring is one way to push back. I still stand by what I say, I find
the requirement of disclosure (regardless of whether it comes from an
Assisted-by tag or something else) helpful for the middleground cases
that don't necessarily require being ignored.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-10-13 13:56 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  8:31 [PATCH] docs: remove Assisted-by references Sasha Levin
2026-10-09  9:38 ` Laurent Pinchart
2026-10-09 10:09   ` Sasha Levin
2026-10-09 10:05 ` Krzysztof Kozlowski
2026-10-09 10:24   ` Greg KH
2026-10-09 15:20   ` Jonathan Corbet
2026-10-11  1:04     ` Steven Rostedt
2026-10-12 15:42   ` Lorenzo Stoakes (ARM)
2026-10-13 11:19     ` Jori Koolstra
2026-10-13 12:38       ` Laurent Pinchart
2026-10-13 12:50         ` Jori Koolstra
2026-10-13 13:01           ` Laurent Pinchart
2026-10-13 13:24         ` Ricardo B. Marlière (SUSE)
2026-10-13 12:49       ` Lorenzo Stoakes (ARM)
2026-10-13 17:16         ` Laurent Pinchart
2026-10-13 12:31     ` Laurent Pinchart
2026-10-13 12:59       ` Lorenzo Stoakes (ARM)
2026-10-13 13:04         ` Krzysztof Kozlowski
2026-10-13 13:07           ` Lorenzo Stoakes (ARM)
2026-10-13 13:12         ` Laurent Pinchart
2026-10-13 13:29           ` Lorenzo Stoakes (ARM)
2026-10-13 13:37             ` Jori Koolstra
2026-10-13 14:52             ` Kees Cook
2026-10-13 14:54               ` Jori Koolstra
2026-10-13 14:58               ` Jori Koolstra
2026-10-13 17:12                 ` Kees Cook
2026-10-13 17:42                   ` Laurent Pinchart
2026-10-13 19:25                     ` Kees Cook
2026-10-13 20:16                       ` Laurent Pinchart
2026-10-13 15:02               ` Lorenzo Stoakes (ARM)
2026-10-13 16:58                 ` Kees Cook
2026-10-13 17:32             ` Laurent Pinchart
2026-10-13  4:24 ` Kees Cook
2026-10-13  5:56   ` Randy Dunlap
2026-10-13  6:18     ` Greg KH
2026-10-13  8:25     ` Kees Cook
2026-10-13 12:28       ` [PATCH] docs: remove Assisted-by reference Jori Koolstra
2026-10-13 12:55         ` Laurent Pinchart
2026-10-13 13:03           ` Jori Koolstra
2026-10-13 13:10             ` Laurent Pinchart
2026-10-13 13:20               ` Jori Koolstra
2026-10-13 13:55                 ` Laurent Pinchart [this message]
2026-10-13 15:18           ` Mark Brown
2026-10-13 17:07             ` Laurent Pinchart
2026-10-13 20:01               ` Shuah Khan

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=20261013135559.GA161185@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=jkoolstra@xs4all.nl \
    --cc=joe@perches.com \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.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.