He doesn’t really specify use cases beyond Sashiko (I believe that’s the project they’re discussing), which, if I understand correctly, uses an LLM to review kernel patches using a pre-set list of prompts. The output of those prompts presumably gets added to the PR for anyone who cares to read it.
These outputs sometimes have mistakes in them, so the maintainers must read them with a critical eye, but I think Linus is arguing here that it’s sufficiently… “good enough” that including them is helpful to the maintainers, that it catches enough real stuff without wasting too much time on fake stuff. There are always tradeoffs when adding a tool to the stack, and sufficiently rare misfires are probably worth the times it catches real problems that humans miss.
He doesn’t really specify use cases beyond Sashiko (I believe that’s the project they’re discussing), which, if I understand correctly, uses an LLM to review kernel patches using a pre-set list of prompts. The output of those prompts presumably gets added to the PR for anyone who cares to read it.
These outputs sometimes have mistakes in them, so the maintainers must read them with a critical eye, but I think Linus is arguing here that it’s sufficiently… “good enough” that including them is helpful to the maintainers, that it catches enough real stuff without wasting too much time on fake stuff. There are always tradeoffs when adding a tool to the stack, and sufficiently rare misfires are probably worth the times it catches real problems that humans miss.