On Fri, 9 Jan 2026 10:54:46 +0200
Laurent Pinchart <[email protected]> wrote:

> > Which is why I'm tiring myself out with this thread when I have a lot of 
> > other
> > things to do :)  
> 
> Thank you for that. As a lurker in this mail thread, I really appreciate
> your efforts as they're saving the time I would need to argue as
> strongly as you do :-)

And even though I'm arguing with Lorenzo, I appreciate him giving his
feedback. I'm not at all frustrated with him, and his arguments help me
understand my own ideas about this document.

> 
> While I agree with the argument that kernel documentation should not
> cover every single hypothetical case that one could come up with, the
> issue at hand here is real (based on the multiple people who have
> replied saying they have seen it happen), and I don't think anyone
> expects the problem to disappear magically given the industry trend.
> 
> It is also absolutely true that actors with questionable ethics will not
> care about the documentation. I do see value in being able to point
> developers acting in good faith to the rules, but an even more important
> point in my opinion is the message your proposal gives to maintainers.

I'm actually not against a document that is all about AI slop. I'm just
against hijacking this document into being that. This wasn't the purpose of
this document. In the TAB, where we started discussing this (and I was
supposed to be the one that wrote the first version, but thankfully Dave
did a great job at getting it going). The focus was to be to document what
we currently do in practice when it comes to tool-generated content. Notice
that the subject of this document doesn't even mention AI.

I personally (and I hope others do too) want to keep this document focused
on transparency when it comes to tool-generated content which also includes
testing and such.

Now, in the future there may be a need for a harsher document to cover AI
slop. I just don't want it to be this document.

I don't think AI is just another tool, but in this document it is, as the
focus was to talk about all tooling that generates patches (which is
everything from sed scripts to AI). I don't want this document to be
focused on AI at all.

If you want something to point to when you receive AI slop, create a
separate document that is for that purpose only. It will keep this document
clearer and also be more useful to the one that needs to read the AI slop
document, as it will be explicitly for them.

-- Steve

Reply via email to