12:02:42 <jki> #startmeeting CIP IRC weekly meeting
12:02:42 <collab-meetbot> Meeting started Thu Jan  8 12:02:42 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02:42 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:42 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:02:46 <jki> #topic AI review
12:02:53 <jki> none on the list
12:03:15 <jki> 5
12:03:17 <jki> 4
12:03:18 <jki> 3
12:03:19 <jki> 2
12:03:21 <jki> 1
12:03:23 <jki> #topic Kernel maintenance updates
12:03:42 <uli_> i pushed 4.19 and 4.4
12:03:51 <pave1> I did reviews: 6.1.63 and .64, and a lot of Renesas patches.
12:04:12 <iwamatsu__> I reviewed 6.12.62 and 63,and  renesas patches.
12:04:12 <pave1> We are down to MSTOP + I3C to review now.
12:04:21 <masami> This week reported 16 new CVEs and 0 updated CVEs.
12:04:40 <iwamatsu__> pave1: about MSTOP patches, I am reviewing
12:04:52 <pave1> Big change with me is that Denx is shutting down, and Nabla is replacing it.
12:05:01 <pave1> ...so please update my email with pavel@nabladev.com.
12:05:06 <pave1> iwamatsu: Thanks!
12:05:51 <pave1> iwamatsu: There's v1 and v2 of the MSTOP patches. Last time I looked, v1 looked like better approach.
12:06:41 <iwamatsu__> Pave1: I see. I will check v1 too.
12:08:37 <jki> i had to debug two stable regressions these days as well
12:13:59 <pave1> Ouch. It seems like jki has connection problem.
12:15:04 <iwamatsu__> hmm
12:15:42 <iwamatsu__> move to next topic?
12:16:10 <pave1> I guess so. We can revisit if he reappears.
12:16:38 <pave1> 5
12:16:39 <pave1> 4
12:16:40 <pave1> 3
12:16:41 <pave1> 2
12:16:42 <pave1> 1
12:17:00 <pave1> *** topic: Kernel release status
12:17:21 <jki> still there?
12:17:39 <pave1> Still here. We are ready
12:17:43 <jki> I'm facing client issues
12:17:45 <pave1> to move to kernel release status if that's ok.
12:17:53 <jki> yes, I tried
12:17:56 <jki> retrying
12:18:11 <jki> #topic Kernel maintenance updates
12:18:18 <jki> ok, now it worked
12:18:22 <pave1> Good :-)
12:18:28 <jki> lot of delayed -rt releases
12:18:37 <pave1> 4.4-rt is due. Uli released kernels so I should be able to do it now.
12:19:46 <pave1> I'll check the dates on rest.
12:20:10 <jki> lost the client again
12:20:26 <jki> so, plans for 5.10-rt and 6.1-rt as well?
12:21:02 <jki> pavel: ?
12:21:09 <pave1> I'll check the dates and do the releases.
12:21:16 <iwamatsu__> 5.10. y-cip-rt seems ready for release.
12:21:41 <jki> both are due
12:22:06 <pave1> So I'll do the releases :-)
12:22:19 <jki> ok, perfect
12:22:33 <jki> anything else regarding releases?
12:22:57 <jki> 5
12:22:58 <jki> 4
12:23:00 <jki> 3
12:23:01 <jki> 2
12:23:03 <jki> 1
12:23:05 <jki> #topic Kernel testing
12:23:15 <patersonc> I'm travelling at the moment so a limited update from me... We now have a couple of beaglev-fire boards online in our lava setup. New TI boards should be shipping next week.
12:23:33 <patersonc> Setup of new TI lab is just starting
12:24:06 <pave1> Tests on mcom are failing. I'm ignoring the failures for now.
12:24:13 <arisut_> from me not so much ether, working on a new release for kci-dev and added deb packages on new releases
12:24:33 <arisut_> also working on making kci-dev a library for been integrated with other tools
12:24:34 <jki> pavel: which tests?
12:24:50 <patersonc> Seem to have a lot of boot issues in kernelCI, e.g. G1M, but I haven't investigated further yet.
12:24:57 <iwamatsu__> One reason is that there is only one mcom device.
12:24:58 <patersonc> Mcom board is offline
12:25:10 <pave1> All tests, afaict: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2250334613 is an example
12:25:32 <jki> ah, I see
12:25:34 <pave1> It says 0 available boards, so not a "real" failure.
12:25:38 <arisut_> will be possible to use kci-dev both as stand alone client tool and as library
12:25:39 <jki> let me ping Pasquale
12:25:54 <patersonc> arisut_: nice
12:26:21 <patersonc> We need to get all the mcom boards merged under the same device-type name
12:26:47 <patersonc> Then we'd have 3
12:28:33 <jki> where is the 3rd?
12:29:10 <jki> the mcom-mtda is differently configured
12:29:33 <patersonc> Can it run the same s/w though?
12:29:49 <jki> I just started discussion with colleagues here how to scale out mtda setups, and then also make sure that we can still run normal kernelci
12:30:21 <patersonc> Okay great. Thanks Jan
12:31:02 <patersonc> I thought we had two mtda devices in the lab, looks like only 1 now
12:31:17 <jki> still only one
12:31:36 <jki> the second one was/is planned for Prague
12:31:42 <jki> but still on the todo list
12:33:07 <jki> more on testing?
12:33:35 <jki> 5
12:33:38 <jki> 4
12:33:39 <jki> 3
12:33:41 <jki> 2
12:33:42 <jki> 1
12:33:44 <jki> #topic AOB
12:34:00 <jki> I won't be able to run next week's meeting
12:34:08 <jki> who can take over?
12:34:23 <pave1> I can do it.
12:34:32 <jki> pavel: TIA!
12:34:40 <pave1> AFAICT there's Zoom meeting on 13th?
12:34:46 <pave1> TSC?
12:35:04 <jki> that is also true - I was referring to the irc meeting
12:35:20 <jki> (but I will likely be absent for the TSC as well)
12:35:25 <pave1> I know. I may or may not be able to make it on 13th.
12:36:14 <pave1> ...so apologies in advance if I can't make it.
12:37:30 <iwamatsu__> If that happens, I'll do it.
12:38:07 <pave1> I meant -- I can make it to irc on 15th. Not sure I can make it to Zoom on 13th.
12:38:51 <jki> I think we can skip the kernel WG on the 13th, not much news I guess
12:39:36 <jki> anything else for today?
12:40:15 <jki> 5
12:40:17 <jki> 4
12:40:19 <jki> 3
12:40:20 <jki> 2
12:40:22 <jki> 1
12:40:24 <jki> #endmeeting