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

Konstantin Ryabitsev <[email protected]> Fri, 17 Jul 2026 10:32:28 -0400
Newsgroups dev.linux.lists.ksummit
Message-ID <20260717-armored-therapeutic-sawfly-e7a3e0@lemur>
On Fri, Jul 17, 2026 at 04:24:15PM +0200, Andrew Lunn wrote:
> > I'd go so far as to say that we DON'T want to feed unfiltered LKML archives
> > into the model -- we probably want to lean on the work done by the cregit
> > folks to identify patch sets that were actually accepted and then work
> > backwards, creating a subset of LKML that resulted in accepted contributions.
> 
> I'm not an LLM person....
> 
> Is there no value in looking at patches which got rejected, and why
> they got rejected, as a template what not to do?

There is, but this is part of the "tuning" bit that I said would be needed and
this would require significant amounts of work. First of all, patches would
need to be considered within the context of the entire discussion, not by
themselves. Subsequent series (v1, v2, vN) would need to be grouped together
and consumed within the same context. Series that resulted in no reviews and
no commits will need to be given a special consideration, because we have no
context why they weren't accepted. It's possible that it was great code that
got missed because the maintainer was overloaded, or if it's useless junk that
nobody even bothered to deign with a response.

So, yeah, we have tons of data, but to be useful for training a model, it will
need to be carefully filtered and weighted.

-K