12:01:02 <jki> #startmeeting CIP IRC weekly meeting
12:01:02 <collab-meetbot> Meeting started Thu Jun  4 12:01:02 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:02 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:02 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:07 <jki> #topic AI review
12:01:11 <jki> none
12:01:18 <jki> 5
12:01:20 <jki> 4
12:01:21 <jki> 3
12:01:23 <jki> 2
12:01:24 <jki> 1
12:01:26 <jki> #topic Kernel maintenance updates
12:01:38 <masami> This week reported 172 new CVEs and 256 updated CVEs.
12:01:41 <uli> doing 4.4 atm
12:01:53 <pave1> I am reviewing 6.1.91 and .92.
12:02:16 <iwamatsu> I reviewed 6.12.88 and 89, and  I am reviewing 90 and 91
12:03:47 <jki> anything to add?
12:04:03 <jki> 5
12:04:05 <jki> 4
12:04:06 <jki> 3
12:04:08 <jki> 2
12:04:10 <jki> 1
12:04:12 <jki> #topic Kernel release status
12:04:18 <jki> all on track
12:04:31 <jki> any issues ahead?
12:04:38 <pave1> Yep. 6.1-rt-cip is due soon, and still
12:04:50 <pave1> no suitable -rt. I may have to do release
12:04:59 <pave1> without having -rt bae.
12:05:17 <pave1> base.
12:05:32 <jki> next RT stable would be tomorrow, if you like to sync
12:05:47 <pave1> If it is then great! :-)
12:06:18 <jki> do you have the invite? I could forward otherwise
12:06:42 <pave1> Aha, you mean stable rt meating, not stable rt release.
12:06:46 <pave1> Yes, I have invite.
12:07:01 <jki> nope, haven't heard of any release :)
12:07:07 <jki> yes, the call
12:07:42 <pave1> Scheduling conflict on that one :-(, but I guess I can just email and ask.
12:07:52 <jki> ok
12:08:10 <jki> then move on?
12:08:18 <jki> 5
12:08:21 <jki> 4
12:08:23 <jki> 3
12:08:25 <jki> 2
12:08:27 <jki> 1
12:08:29 <jki> #topic Kernel testing
12:09:50 <patersonc> Hi (sorry for the delay)
12:10:12 <patersonc> I'm currently trying to get the T2H boards back online in the Renesas LAVA lab.
12:10:40 <patersonc> Munich lab is still offline
12:11:09 <patersonc> T2H bootloaders need an update, then they should work with KernelCI test jobs, then I'll merge that support
12:12:15 <patersonc> I think that's it from me
12:12:30 <jki> Munich will be restored next week
12:12:40 <patersonc> iwamatsu: Can you let me know once you've updated your T2H board? Let me know if you need any help
12:12:44 <patersonc> Thanks jki
12:12:55 <jki> Prague should be fine now
12:13:14 <iwamatsu> patersonc: OK
12:13:23 <patersonc> Thanks
12:14:33 <jki> more on testing?
12:14:45 <patersonc> _o_
12:15:19 <jki> 5
12:15:21 <jki> 4
12:15:22 <jki> 3
12:15:24 <jki> 2
12:15:26 <jki> 1
12:15:28 <jki> #topic AOB
12:15:44 <jki> I had one topic
12:15:47 <jki> AI-assisted backport reviews, state & approaches
12:16:04 <patersonc> Very on-trend
12:16:15 <jki> uli told me, and some should have been on CC, that he is using it for a while
12:16:31 <jki> I was wondering what others are doing
12:16:59 <jki> and if we could share skills or whatever centrally
12:17:21 <uli> for those who have not received that mail: i'm basically dumping all commits into an llm before release, with a large diff context and a slightly more verbose version of "check if this breaks something"
12:17:36 <uli> works pretty well for me, i.e. it finds things that would have otherwise slipped through
12:18:09 <patersonc> nice
12:18:40 <pave1> Yeah, I see how it can be useful with big context.
12:18:50 <pave1> I don't have access to suitable llm that could be used for this.
12:18:58 <iwamatsu> I'm testing Sashiko locally.
12:18:59 <patersonc> Is there a thought/plan to convert to some kind of "official" CIP tooling? Or do we re-purpose/contribute to what Sasha has been working on?
12:19:26 <jki> is anyone tracking Sasha's work in more details?
12:20:03 <pave1> For the tooling... there could be improvements to what we have, too.
12:20:12 <jki> I suspect it could eventually end up in sashiko
12:20:29 <pave1> Half a year ago, 6.12, 6.1 and 5.10 would be in sync, so same patch would be reviewed once.
12:20:39 <pave1> That no longer works.
12:21:13 <pave1> Also maybe collecting outside notes ("John Doe reviewed this patch for 4.19") might be good.
12:21:26 <patersonc> Is Sashiko more about reviewing patches sent to the ML, rather than selecting suitable patches for backporting?
12:22:12 <pave1> patersonc: "Selecting patches for backporting" ... -stable was selecting way too much, so that was not normally a problem.
12:22:20 <pave1> (But maybe AUTOSEL is paused for now or something).
12:22:30 <jki> patersonc: https://lwn.net/Articles/1073583/
12:23:05 <jki> "Levin said that he had been working on getting Sashiko to review backports to stable trees and also needed to provide extra prompts in order to have it focus on the feedback he was looking for."
12:23:27 <patersonc> Ah, splendid :)
12:24:21 <jki> was anyone in contact with Sasha already?
12:24:36 <jki> should we reach out and ask for some info?
12:25:07 <patersonc> I think it could be something really good for CIP to collaborate on, it fits directly into what the project needs - same as stable
12:25:23 <jki> exactly
12:28:03 <jki> is there any mailing list for the sashiko work in general?
12:29:01 <iwamatsu> sashiko@lists.linux.dev
12:29:03 <jki> ah, there is: https://lore.kernel.org/sashiko/ / sashiko@lists.linux.dev
12:29:13 <jki> yeah, just spotted as well,
12:29:22 <patersonc> Nice
12:29:28 <jki> so, step one would be researching for stable work on that list
12:29:54 <jki> step two could be asking Sasha on this list for updates, expressing our interest along this
12:30:13 <jki> uli: would you be interested in starting such a thread then?
12:31:45 <uli> not sure. :) i'll have a look at the list first.
12:32:26 <uli> see what they're actually doing.
12:32:27 <jki> didn't spot anything about stable there yet, didn't find Sasha discussing there either
12:33:44 <jki> ok, let's look at this and discuss next week again, ok?
12:33:52 <uli> good.
12:34:29 <jki> good
12:34:36 <jki> other businesses for today?
12:35:16 <jki> 5
12:35:18 <jki> 4
12:35:20 <jki> 3
12:35:21 <jki> 2
12:35:23 <jki> 1
12:35:24 <jki> #endmeeting