12:02:49 <jki> #startmeeting CIP IRC weekly meeting
12:02:50 <collab-meetbot`> Meeting started Thu Apr 16 12:02:49 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:50 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:50 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:02:56 <jki> #topic AI review
12:03:02 <jki> none
12:03:13 <jki> 5
12:03:15 <jki> 4
12:03:16 <jki> 3
12:03:19 <jki> 2
12:03:20 <jki> 1
12:03:24 <jki> #topic Kernel maintenance updates
12:03:38 <masami> This week reported 16 new CVEs and 12 updated CVEs.
12:03:46 <uli_> pushed 4.19, will do 4.4 next
12:03:52 <iwamatsu> I am revieweing 6.12.80
12:04:04 <pave1> I was reviewing 6.12.81, .82
12:04:44 <jki> anything else?
12:05:00 <jki> 5
12:05:02 <jki> 4
12:05:04 <jki> 3
12:05:05 <jki> 2
12:05:07 <jki> 1
12:05:10 <jki> #topic Kernel release status
12:05:28 <jki> 4.4 is due, will come soon as Uli just said
12:05:55 <jki> 4.19-rt: what is now the conclusion?
12:06:17 <pave1> Lets do a release next
12:06:34 <pave1> month after 4.19-cip is released.
12:06:54 <pave1> That way code is not too old
12:07:25 <pave1> and we don't have too many releases.
12:07:31 <jki> you mean do a release for -rt soon after the next regular 4.19-cip release?
12:07:43 <jki> yeah, that is the point of this old kernels
12:07:45 <pave1> yes.
12:07:49 <jki> ok, noted
12:08:18 <jki> anything else on releases?
12:08:34 <jki> 5
12:08:36 <jki> 4
12:08:37 <jki> 3
12:08:39 <jki> 2
12:08:40 <jki> 1
12:08:42 <jki> #topic Kernel testing
12:08:52 <patersonc> Hey.
12:09:00 <patersonc> We still have some boards offline in the SIemens lab
12:09:21 <jki> which Siemens lab?
12:09:25 <patersonc> Although the lab is at least back online now since yesterday
12:09:36 <patersonc> 3 offline in Prague. 1 in Munich
12:09:57 <jki> will clarify
12:10:27 <patersonc> Thanks
12:10:40 <patersonc> Nothing else to report from my side
12:11:25 <jki> patersonc: do you have email notifcation options for the worker or device states?
12:12:15 <patersonc> Emails get sent to cip-testing-results@lists.cip-project.org when a healthcheck fails, but they probably get lost in a lot of traffic
12:12:58 <jki> yeah, only state changes, and that for boards someone is responsible for
12:13:36 <jki> btw, the riscv board in the MUC lab is only planned, was never brought online
12:14:02 <patersonc> Gotcha
12:14:10 <jki> we were considering to enable it with image support (mtda) but that work got delayed
12:15:14 <jki> and did "riscv" mean "beaglev"? you once created that, patersonc
12:15:36 <jki> the beaglev-fire are a different device type
12:15:40 <patersonc> No. Beaglevs are here: https://lava.ciplatform.org/scheduler/device_type/beaglev-fire
12:16:12 <jki> exactly
12:16:50 <jki> I have a fire with my, currently not wired up with a lab, that could join the pool once we have time - and need
12:17:07 <jki> or we have an mtda setup to run full images on it
12:17:31 <patersonc> That would be more useful me thinks
12:18:28 <jki> then I guess that generic "riscv" device can go again - or keep it and rename it?
12:18:55 <patersonc> It would probably be better to be more specific
12:20:10 <jki> ok, will talk to Quirin about that one
12:20:15 <jki> anything else on testing?
12:20:48 <patersonc> Not from me
12:21:38 <jki> then let's move on...
12:21:42 <arisut> no
12:21:48 <jki> 5
12:21:50 <jki> 4
12:21:52 <jki> 3
12:21:54 <jki> 2
12:21:55 <jki> 1
12:21:58 <jki> #topic AOB
12:22:32 <jki> uli_: thanks for reminding of Embedded Recipes!
12:22:44 <uli_> np
12:22:47 <jki> will not go there as well, not sure who else plans that
12:22:59 <jki> some tickets still left
12:23:37 <uli_> i'm still waiting for yoshi's final approval, though. but i guess the conditions are met.
12:26:06 <jki> will ping him again
12:26:13 <jki> ok, other topics for today?
12:26:13 <uli_> thx
12:26:40 <jki> 5
12:26:42 <jki> 4
12:26:44 <jki> 3
12:26:45 <jki> 2
12:26:47 <jki> 1
12:26:49 <jki> #endmeeting