From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Sasha Levin <sashal@kernel.org>,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.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,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Justin Stitt <justinstitt@google.com>,
Carlos Maiolino <cem@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Jori Koolstra <jkoolstra@xs4all.nl>,
Brian Foster <bfoster@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
David Disseldorp <ddiss@suse.de>, Mark Brown <broonie@kernel.org>,
Jani Nikula <jani.nikula@intel.com>, Jens Axboe <axboe@kernel.dk>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
"Christian Brauner (Amutable)" <brauner@kernel.org>
Subject: Re: [PATCH] docs: remove Assisted-by references
Date: Wed, 21 Oct 2026 00:15:32 +0300 [thread overview]
Message-ID: <20261020211532.GD15441@killaraus.ideasonboard.com> (raw)
In-Reply-To: <atI_TSQXzAQFWBfx@gremlin>
On Fri, Oct 16, 2026 at 05:14:02PM +0100, Lorenzo Stoakes (ARM) wrote:
> On Tue, Oct 13, 2026 at 07:32:40PM +0200, Laurent Pinchart wrote:
> > > Yes there will be collateral damage, but it's that or no more open source (we're
> > > not the only ones going through this!)
> >
> > Think how you will feel the day you will be treated as collateral
> > damage.
>
> I'm already working evenings and weekends to deal with AI slop to the point
> of burnout (finished work at 9pm last night, for instance), so I already
> feel like I'm collateral damage.
>
> And it's utterly thankless work. You get negativity no matter what you do
> with this stuff.
>
> I accept all that, I do it because I care. So you take it on the chin. But
> the AI slop wave has changed everything.
>
> What was already an unsustainable review load has now doubled, or tripled,
> and there's every reason to believe it's only the beginning.
>
> So now maintainership and review is thankless at an unprecedented scale,
> which leads to only one thing - burnout. Possibly even the medical variety,
> where you don't come back for a long while, if ever.
I hear your pain, and I'm sure it's more painful than what I experience
in my corner of the kernel. I know how the sense of duty feels as a
maintainer. It may not make a big difference, but I want to say you have
no duty to burn out. If you decided to slow down merging patches in MM
to get more sleep until we find a better solution to cope with the
unsustainable work load, I would support that.
> The project simply cannot function like this, it can't. And nothing that
> requires per-submitter effort scales.
>
> There are people sending 500 patches in 2 hours already, for instance.
>
> The only solution that can possibly work is large-scale ignoring, because
> the number of submissions can grow exponentially, and even small
> effort-per-submission is vastly beyond available resource.
It increasingly feel we need to also look at long term solutions.
There's a sort of knee-jerk short term reaction that I can understand.
On the longer term, I agree with Lyude that any solution will involve
increasing the number of reviewers and maintainers.
I fully understand that many maintainers currently feel they're too
pressured to invest time in the next generation. We need to find
solutions to make that possible.
> The alternative is maintainers quitting en masse and the project dies at that
> point. So it's a choice between two bad options, but one of them is 'linux
> dies'. So the other one seems better.
If we stop investing in the next generation, the project will die too,
in a worse way in my opinion.
> > I find this mail thread it taking an almost cynical and violent turn.
> > Are people rejoicing at the prospect of actively discriminating against
> > sincere contributors, or am I misreading it ? The kernel community needs
> > more care.
>
> You're misreading it.
>
> I feel _terrible_ for newcomers. Really. It hurts me that this situation
> exists.
>
> I came up as a hobbyist from nowhere. I wrote a book thinking nobody would
> care, part-time, while doing a busy non-kernel job.
>
> And the kernel being what it is let me get where I am, for which I'm
> eternally grateful.
>
> I want to encourage talented newcomers. They are rare, and are the future
> of the kernel.
>
> I explicitly spent time at LPC encouraging newer people, in person, for
> instance. I have (often behind the scenes) encouraged young, talented
> developers. So in general, I've _actively_ worked on this.
>
> And new people sending small, sensible, non-slopped patches/series will
> still most likely get their stuff merged in mm.
>
> So it's very far from the case of 'oh wow now I can just ignore everybody'.
Thank you for taking the time to clarify this. I'm happy to read I
misunderstand you. E-mail communication is horrible to discuss these
topics, especially in public.
This is something we really need to improve quickly. Over the past week
multiple active kernel developers asked me if I thought they needed to
find a job elsewhere, thinking maintainers will now ignore anything but
perfect patches and dismiss contributions from developers who don't use
LLMs. That's a wrong impression (at least I very much hope so, and you
clarified that you're not advocating for that), but it's a disastrous
impression that many people got from the maintainers summit and the
following mailing lists discussions.
I'd like to see more maintainers clarifying this publicly, like you have
done.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-10-20 21:15 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:31 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 20:45 ` Linus Torvalds
2026-10-14 13:56 ` Lorenzo Stoakes (ARM)
2026-10-16 14:19 ` Matthew Brost
2026-10-17 17:42 ` Troy Benjegerdes
2026-10-19 17:41 ` lyude
2026-10-14 18:47 ` Kees Cook
2026-10-15 23:14 ` Jeremy Dean Clifton
2026-10-13 15:02 ` Lorenzo Stoakes (ARM)
2026-10-13 16:58 ` Kees Cook
2026-10-13 17:32 ` Laurent Pinchart
2026-10-16 16:14 ` Lorenzo Stoakes (ARM)
2026-10-20 21:15 ` Laurent Pinchart [this message]
2026-10-14 3:23 ` Theodore Tso
2026-10-14 11:23 ` Mark Brown
2026-10-14 13:08 ` Jori Koolstra
2026-10-14 13:42 ` Lorenzo Stoakes (ARM)
2026-10-14 14:15 ` Mark Brown
2026-10-19 22:44 ` Laurent Pinchart
2026-10-20 4:28 ` Theodore Tso
2026-10-19 16:32 ` lyude
2026-10-19 22:24 ` Laurent Pinchart
2026-10-19 16:26 ` lyude
2026-10-16 18:26 ` Ihor Solodrai
2026-10-19 16:21 ` lyude
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
2026-10-19 16:50 ` lyude
2026-10-13 15:18 ` Mark Brown
2026-10-13 17:07 ` Laurent Pinchart
2026-10-13 20:01 ` Shuah Khan
2026-10-19 16:15 ` lyude
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=20261020211532.GD15441@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=apw@canonical.com \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=cem@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=ddiss@suse.de \
--cc=federico.vaga@vaga.pv.it \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jani.nikula@intel.com \
--cc=jkoolstra@xs4all.nl \
--cc=joe@perches.com \
--cc=justinstitt@google.com \
--cc=krzk@kernel.org \
--cc=kuba@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=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
all inboxes | Powered by JetHome®