12:01:51 <jki> #startmeeting CIP IRC weekly meeting
12:01:51 <collab-meetbot> Meeting started Thu Jan 22 12:01:51 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:51 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:51 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:56 <jki> #topic AI review
12:02:04 <jki> list empty, once again
12:02:09 <jki> 5
12:02:10 <jki> 4
12:02:12 <jki> 3
12:02:14 <jki> 2
12:02:15 <jki> 1
12:02:17 <jki> #topic Kernel maintenance updates
12:02:37 <pave1> It seems we have finally catched up with torrent of Renesas patches.
12:02:37 <masami> This week reported 2 new CVEs and 6 updated CVEs.
12:02:56 <jki> nobuhiro wrote: I am reviewing 6.12.66.
12:02:57 <uli> i'm working on the next 4.19
12:03:06 <pave1> Otherwise reviews: 6.1.66.
12:04:06 <jki> anything to add?
12:04:15 <jki> 5
12:04:17 <jki> 4
12:04:19 <jki> 3
12:04:20 <jki> 2
12:04:22 <jki> 1
12:04:24 <jki> #topic Kernel release status
12:04:36 <pave1> So.. we don't have a goot match for 6.1-rt.
12:04:55 <jki> when would the next 6.1-rt appear, likely?
12:05:04 <jki> did you ask?
12:05:04 <pave1> I asked rt maintainers for information.
12:05:07 <jki> ok
12:05:12 <jki> reply?
12:05:39 <pave1> I'm waiting for reply, don't ask _when_ I asked :-).
12:05:53 <jki> ok :)
12:06:09 <pave1> But last release is at "Nov 10", so... hopefully one is near.
12:06:18 <jki> indeed
12:06:50 <jki> give another week, then discuss if own forward porting is possible
12:07:06 <pave1> yep.
12:07:37 <jki> nobuhiro wrote he plans to release a 6.12 tomorrow
12:07:40 <jki> ok
12:07:46 <jki> other issues in sight?
12:08:14 <jki> 5
12:08:16 <jki> 4
12:08:17 <jki> 3
12:08:19 <jki> 2
12:08:21 <jki> 1
12:08:22 <jki> #topic Kernel testing
12:08:50 <patersonc> No updates from me
12:09:11 <arisut_> same
12:09:54 <jki> the mcom in Prague is getting closer to be online again
12:10:00 <jki> likely early next week
12:10:05 <patersonc> Great. Thanks
12:10:15 <pave1> Good, that will mean one less "fail" on testing.
12:11:05 <jki> if there are no other testing topics...
12:11:15 <jki> 5
12:11:17 <jki> 4
12:11:19 <jki> 3
12:11:21 <jki> 2
12:11:22 <jki> 1
12:11:25 <jki> #topic AOB
12:11:26 <pave1> I'll be at FOSDEM at end of month, talking about cameras.
12:11:32 <pave1> Does anyone else plan FOSDEM?
12:11:43 <jki> yep, will be there as well
12:12:15 <jki> my colleague do the work (talking) :)
12:12:44 <jki> (unified kernel ftrace + lttng-us)
12:13:08 <pave1> Nice!
12:13:37 <jki> pavel: we can meet, just drop me a note, or we see us in the embedded track ;)
12:13:38 <patersonc> I have a question about linux-stable-rt. I noticed this week there is a v6.12 branch. Are we monitoring this for patches to integrate into 6.12-cip?
12:14:24 <jki> do my understanding: no. those are out-of-tree /wrt 6.12 mainline
12:14:26 <pave1> jki: Yes, I guess it will somehow work out :-).
12:14:58 <pave1> patersonc: realtime was merged into mainline in 6.12.
12:15:04 <jki> the 6.12-rt branch contains rt bits not in 6.12 stable, and we only track stable /wrt rt so far
12:15:22 <jki> and we have no backports of further rt patches from newer upstream kernels yet
12:15:50 <jki> once that should change, monitoring stable trees might become useful
12:15:50 <pave1> So we don't have separate -cip-rt branch, and we don't monitor 6.12-rt branch ... as those are features, not bugfixes.
12:15:57 <patersonc> okay
12:16:22 <patersonc> It looks like they added arm32 support
12:16:33 <jki> into updstream now as well?
12:16:42 <patersonc> Into that 6.12 branch
12:16:48 <jki> in 6.12-rt for sure
12:17:12 <jki> we are waiting for upstream arm32-rt, then we could backport to 6.12-cip
12:17:33 <pave1> So siemens is still interested in arm32?
12:17:37 <jki> sure
12:17:47 <jki> and not only us
12:17:57 <pave1> Be warned that there are powerful forces trying to get rid of everything 32bit.
12:17:59 <jki> TI, I guess Renesas as well
12:18:19 <jki> pavel: we sat in the same talk, and the message was clear: not in the next decade
12:18:55 <pave1> :-)
12:18:59 <jki> hw is still being produced, though not really new one
12:19:33 <pave1> Well, I guess those powerful forces really hate HIGHMEM.
12:19:41 <pave1> Avoid HIGHMEM and you could be ok.
12:19:57 <jki> right
12:20:34 <jki> think Arnd has this on the radar and will communicate plans / ask for further feedback
12:22:29 <jki> any other business for today?
12:23:14 <jki> 5
12:23:16 <jki> 4
12:23:17 <jki> 3
12:23:19 <jki> 2
12:23:22 <jki> 1
12:23:23 <jki> #endmeeting