Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc

--aJJ62qiVOp1Pxomb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jul 16, 2026 at 12:24:45PM -0400, Sasha Levin wrote:
> On Thu, Jul 16, 2026 at 05:08:40PM +0100, Mark Brown wrote:

> > The issue (which a number of projects are facing) is as much one of
> > volume as anything else, the code generation machines are enabling the
> > generation and submision of volumes of code where things were previously
> > constrained by human factors.  It can turn into a bit of a DoS.  I don't
> > have any particularly bright ideas here but it's definitely a thing.

> Sure, we're seeing quite the increase in patch submissions, but I'm trying to
> argue that the issue isn't a new one: lack of maintainers, trusted reviewers,
> and maintainer burnout has been a topic at each kernel summit for as long as I
> can remember. AI just kicks it up a notch.

> My concern is that if we focus on the AI aspect, we still won't be solving the
> underlying issue.

My experience is that the AI stuff is qualtatively quite different to
the general pattern there, the human factors are a big part of it as is
the fact that unlike other tooling it's not doing anything regular or
predictable so you can't develop confidence in the tooling in the same
way you might otherwise.  This all makes the back pressure that helps
mitigate things less effective.

> I'm hoping we can figure out how to get maintainers great tooling, testing, and
> community, rather than figuring out how to block a developer who uses LLM.
> Maybe AI would actually be a great catalyst for that as well?

There's a money question there of course, I note that my own out of
pocket expenses for non-LLM tooling are non-zero and there's an
economic concern among the various concerns about the LLM stuff.

I do also think there's a place for a conversation about trying to get
the people using these tools to do so in a way that's easier to deal
with, a huge portion of the issues people have with them are to do with
externatilities that they create.

--aJJ62qiVOp1Pxomb
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpaO2MACgkQJNaLcl1U
h9DcXgf/SdEAKAJuw2LNXUMjEbWT03fsbiNeaBZG7oK4d2H1VkSNms+Qnk5UnhVw
NBoIZTmespc/gOiFaf6HJiU38bmciOSvpCLvH7VFDyOx9Oh2VL6z1a7U0sFFAgW+
rn4TyDOxciJugyKD6f0c1+BlhY3f4YpOYBfvwWEQC8oC0OavwbVQXiLq/fc1xc34
HT6KJoawFdj6BdzFiYKQZUpCNUpA/qoEvTu+wu28nsu1+LdKyW8dTYV6jPTraxjz
2B6rxMZcvcVLW+a8dGWEvaaDDweHUKOj7lhPZZpf7NRpaRwIi90mKyfsdJXMIyAi
qKyttFLDCBpSR2/oziQHLN+hN8p8JA==
=VDKN
-----END PGP SIGNATURE-----

--aJJ62qiVOp1Pxomb--