Re: Request for review for 4.19-st20, 4.19-cip136

[Ulrich Hecht <uli@fpond.eu>]

> On 09/03/2026 11:00 AM CEST Pavel Machek <pavel@nabladev.com> wrote:
> > Here are the "manual" backports for the upcoming 4.19 kernel
> >  release. There's a total of 68; 40 by me, and 28 by LLM. (The latter
> >  are labeled with "Assisted-by: SLTR:qwen-3.8".)
> 
> I'm not huge fan of "the more the better" here.

There were 1300 patches incoming this release cycle; the number of backports reflects that. If you see classes of fixes that should not be backported I can ignore those in the future. (I have sent you the prompt I'm using for triage.)

> We are not testing all
> of the kernel, we are not even compile testing all of it

I am doing the latter.

>, so bugs will
> eventually creep in.

Right now it looks to me as if this approach reduces the number of bugs. The LLM has more time to look into backports and was able to find differences in 4.x that I would have not found because of that.

> Can you clarify what role LLM had here, what goals you set for it, and
> how you reviewing the stuff?

- The added bit that produces the backports is simply "If applicable, write out a modified version of the patch that applies to the legacy code base."
- The patches marked with the Assisted-by tag have been applied by me as written by the LLM.
- I'm reviewing the auto-generated backports manually as well as using the review prompt as found in the SLTR repository.

CU
Uli