Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc
Mark Brown <[email protected]> Thu, 16 Jul 2026 17:08:40 +0100
| Newsgroups | dev.linux.lists.ksummit |
|---|---|
| Message-ID | <[email protected]> |
--+4z9Ucn7RZRpfmUz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 16, 2026 at 11:28:25AM -0400, Sasha Levin wrote: > On Thu, Jul 16, 2026 at 09:09:27AM -0600, Jonathan Corbet wrote: > > - There are many first-time contributors coming in with LLM-generated > > patches. At times, I could swear that every one of them is focused on > > Our maintainers are not scaling to handle this new flood, and I fear we > > are going to see some unfortunate things merged. One LLM-driven newco= mer > > recently nearly succeeded in establishing himself as the maintainer of > > lib/. How do we hold the line against this stuff while remaining open= to > > new developers? > Shouldn't it be a merits question rather than a tools question? > If the commits are correct, does it matter if they were written with an L= LM? we > can insist more on supplying tests and demonstrating correctness, somethi= ng we > seem to be doing quite rarely right now. 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=20 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. --+4z9Ucn7RZRpfmUz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpZAgcACgkQJNaLcl1U h9DNmgf/esXygnBM8+rh10kMoRTXokZJCGsGLdXG/ej91b52p0wAsN718U9Hj6y3 aRkf2Ek5dbU8bU/BXXCeXVcfRQnCLgdNDCW29fxw0F9RN6mDVhMBiAsjYTpftzln 3NlX5M8rWplLoxo33o64xOgj/KGagtO1UC+C8YwxPppnaekkIMJZYibFVzhHFgl1 8mtaUqInoTz7dmVmfXnVyOyv7tORm9d56LAnSg9WP3z18sLwVUA3eQkswZtQyPZC x0IcEQRIHYbKD6UEiBZm1Gka3m/P6H7LvXZsk2JoIQAB9ER5cdCq3pWAPwgRSFe6 1k6JWPOMqqrGZD9to6tFS5NABk0ACQ== =JzB0 -----END PGP SIGNATURE----- --+4z9Ucn7RZRpfmUz--