13:02:03 <pave1> #startmeeting CIP IRC weekly meeting 13:02:03 <collab-meetbot> Meeting started Thu Mar 20 13:02:03 2025 UTC and is due to finish in 60 minutes. The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:03 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:03 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting' 13:02:08 <pave1> #topic AI review 13:02:17 <pave1> - share release scripts/procedures [pavel, iwamatsu-san] 13:02:30 <pave1> I guess we should have jki for this one? 13:02:39 <pave1> 3 13:02:41 <pave1> 2 13:02:42 <pave1> 1 13:02:50 <pave1> #topic Kernel maintenance updates 13:03:00 <iwamatsu__> I am going to send it after this meeting. 13:03:06 <pave1> I was reviewing 6.1.131 & .129. 13:03:07 <masami> This week reported 2 new CVEs and 110 updated CVEs. 13:03:09 <pave1> Aha, ok, thank you! 13:03:18 <iwamatsu__> I reviewed v6.1.130. 13:03:22 <uli_> released 4.4 and 4.19 13:03:28 <masami> I updated cip-kernel-sec yaml format to add version information. 13:03:44 <pave1> Plus, 6.12-cip is now started. 13:04:05 <iwamatsu__> masami, pave1: thank you! 13:04:55 <pave1> Thank you, anything else? 13:04:59 <pave1> 3 13:05:00 <pave1> 2 13:05:01 <pave1> 1 13:05:12 <pave1> #topic Kernel release status 13:05:20 <pave1> linux-6.1.y-cip: interval 15 day 13:05:20 <pave1> latest version release date: Wed Mar 5 05:05:09 AM UTC 2025 13:05:20 <pave1> limit date: Thu Mar 20 05:05:09 AM UTC 2025 13:05:20 <pave1> Status: *Late* 13:05:20 <pave1> linux-6.1.y-cip-rt: interval 30 day 13:05:20 <pave1> latest version release date: Fri Feb 14 05:24:30 PM UTC 2025 13:05:21 <pave1> limit date: Sun Mar 16 05:24:30 PM UTC 2025 13:05:21 <pave1> Status: *Late* 13:05:41 <pave1> -cip-rt: I need upstream -rt release for that. I'll ask if it does not appear soon. 13:06:03 <iwamatsu__> I am working for 6.1.y-cip 13:06:42 <pave1> Thank you! 13:06:59 <pave1> 3 13:07:02 <pave1> 2 13:07:03 <pave1> 1 13:07:09 <pave1> #topic Kernel testing 13:07:36 <arisut> working on adding CIP configs to KernelCI 13:07:40 <patersonc> Not much from me. I'm just looking into seeing if we can do without the gitlab-ci file for linux-cip 13:07:58 <pave1> Yep, thank you. 13:08:20 <patersonc> I'd be able to add some default behaviour based on branch name, e.g. run pipeline x if branch y 13:08:31 <pave1> 6.12-cip is in the git, testing it one way or another would be good. 13:08:49 <patersonc> For custom dev branches you may be better to add your own .gitlab-ci still, or you'd have to have known branches per kernel version 13:09:01 <pave1> Basing it on branch name would work for 6.12.cip. 13:09:07 <pave1> Can we do that? 13:09:17 <pave1> iwamatsu: do we have good enough configs to start testing? 13:09:48 <iwamatsu__> pave1: yes. we have enough configs. 13:10:17 <patersonc> They'd need to be copied into a 6.12.y-cip though. And -rt ones added 13:11:05 <pave1> patersonc: Could we get some kind of regexp? Automatically testing test-4.19 as ... 4.19 would make sense, and I could just push into appropriate ci/pavel/test-6.1 or so branch for testing. 13:11:27 <patersonc> pave1: That's what I'm just looking into 13:11:35 <pave1> patersonc: THank you! 13:11:54 <pave1> patersonc: We probably won't have separate branches for -rt in 6.12. 13:12:32 <pave1> patersonc: But its true that separate configs for rt and non-rt configs would still make sense. 13:13:33 <pave1> But even non-rt testing would be useful at this point. I cherry-picked 20 or so renesas patches, verifying it still builds and boots would be good. 13:13:35 <patersonc> With the current way the build scripts work it would actually be better to merge the -rt configs into the non-rt dir if we're not having a separate branch 13:18:36 <pave1> Ok, maybe you can coordinate with iwamatsu-san on the mailing list? I guess we'll need more 13:18:54 <patersonc> Sure 13:19:01 <pave1> input about the rt configurations, for which boards, etc. But we should be able to get basic 13:19:04 <iwamatsu__> Sure. 13:19:07 <pave1> testing going with what we have. 13:19:09 <pave1> Thanks! 13:19:13 <pave1> 3 13:19:13 <pave1> 2 13:19:14 <pave1> 1 13:19:26 <pave1> #topic AOB 13:19:38 <pave1> Anything else? 13:19:49 <pave1> 5 13:19:50 <iwamatsu__> I can not attend next meeting. 13:20:10 <pave1> Ok, thanks for information. 13:20:22 <pave1> 5 13:20:26 <pave1> 4 13:20:28 <pave1> 3 13:20:30 <pave1> 2 13:20:31 <pave1> 1 13:20:43 <pave1> #endmeeting