13:01:38 <jki_> #startmeeting CIP IRC weekly meeting
13:01:38 <collab-meetbot> Meeting started Thu May 22 13:01:38 2025 UTC and is due to finish in 60 minutes.  The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:38 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:38 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:42 <jki_> #topic AI review
13:02:15 <jki_> none recorded, but I should add one for me: "write announcement draft for 6.12-cip"
13:02:28 <jki_> anything else?
13:02:40 <jki_> 5
13:02:41 <jki_> 4
13:02:42 <jki_> 3
13:02:44 <jki_> 2
13:02:45 <jki_> 1
13:02:47 <jki_> #topic Kernel maintenance updates
13:03:04 <pave1> I was reviewing 6.1.138 and 6.12.30.
13:03:15 <masami> This week reported 100 new CVEs and 2 updated CVEs.
13:03:55 <iwamatsu__> I reviewed 6.1.137 and 138
13:05:17 <jki_> anything to add?
13:05:46 <jrherrera> if it is able to said briefly, how difficult has kernel maintenance of the non-lts branches been?
13:05:46 <jki_> 5
13:06:13 <jki_> you mean 4.4 and now 4.19?
13:06:40 <jrherrera> yes
13:07:16 <jki_> ulrich not here today, maybe pavel can comment as well
13:07:20 <pave1> AFAICT uli is not here today, and he's the one that does that work currently.
13:07:56 <pave1> Not sure about "how difficult", but good thing is we can take a look at 5.4.X, and only consider patches
13:07:57 <jrherrera> unfortunate to hear, maybe once Ulrich is back on I can send another comment in the channel
13:08:10 <pave1> that are applied there.
13:08:26 <pave1> And those 5.4.X branches are reasonably quiet now.
13:08:44 <jki_> Ulrich also gave a presentation about 4.4 maintenance at OSSJ in 2023 IIRC
13:09:09 <jrherrera> that makes sense actually, it's quite smart. So the older kernels are similar enough so far that back porting is still not too problematic
13:09:16 <jrherrera> okay! thank you for the answer
13:09:36 <jrherrera> jki_, can you send me the link in the channel or in PMs after the meeting?
13:10:54 <jki_> will try to find it, yet
13:11:21 <jki_> ok, anything else?
13:11:22 <jrherrera> that's fine it's not too urgent so we can move on to the next section
13:11:34 <jki_> 5
13:11:36 <jki_> 4
13:11:38 <jki_> 3
13:11:40 <jki_> 2
13:11:42 <jki_> 1
13:11:44 <jki_> #topic Kernel release status
13:12:04 <jki_> all on track according to our updated schedule
13:12:17 <jki_> still need to update also the wiki after the 6.12 release
13:12:45 <iwamatsu__> I can update it.
13:12:54 <jki_> TIA!
13:13:05 <jki_> do we keep the reporting script somewhere in git?
13:13:13 <jki_> I updated mine only locally
13:13:30 <jrherrera> I'd recommend it
13:13:37 <jki_> cip-release-term.sh
13:13:50 <iwamatsu__> Sure.  I will update script.
13:13:59 <pave1> Yes, it is in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git
13:14:17 <pave1> The wiki: I guess Ulrich should now be marked as 4.19 maintainer.
13:14:28 <jki_> right
13:14:32 <iwamatsu__> OK,
13:14:33 <jki_> that as well
13:14:58 <jki_> ok, will send an MR to that repo
13:16:02 <jrherrera> ok
13:16:16 <jki_> good
13:16:23 <jki_> then let's move on...
13:16:33 <jki_> 5
13:16:35 <jki_> 4
13:16:37 <jki_> 3
13:16:38 <jki_> 2
13:16:40 <jki_> 1
13:16:41 <jki_> #topic Kernel testing
13:16:56 <patersonc> Howdy
13:17:08 <jrherrera> hi!
13:17:15 <arisut> I'm writing a manual about testing CIP kernel with KernelCI kci-dev
13:17:24 <patersonc> Great
13:17:26 <arisut> https://gist.github.com/aliceinwire/4de8692c9e006a2ddf92717fe3aaef06
13:18:04 <arisut> pratically using for example kci-dev checkout --giturl https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git --branch linux-6.1.y-cip --tipoftree
13:18:39 <arisut> will test linux-6.1.y-cip branch on the last commit with KernelCI
13:18:47 <patersonc> Thanks
13:19:09 <arisut> adding --watch will wait for results and print on screen
13:19:39 <arisut> results will be added to the staging or production dashboard so that can be also checked by browser or using kci-dev results
13:20:21 <arisut> if anyone want to start trying it, I can give token by email
13:20:47 <patersonc> yes please
13:21:31 <patersonc> I fixed the 6.12 cip ci pipeline to match better the sub-set of kernel configs we have. So the gitlab ci pipelines for 6.12 should look better now. We're not testing to the same level as other kernels yet but we have a lot less configs this time round. If there is an important gap please let me know.
13:22:13 <patersonc> We/TSC also need to finalise this table: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
13:23:46 <arisut> patersonc, thanks
13:24:52 <arisut> anyone else that want a kci-dev token? just write me a token request by email and I will send it
13:24:57 <arisut> pave1?
13:25:10 <pave1> arisut: Yep, I guess one would be useful.
13:25:35 <arisut> ok give me few days and I will send it to you
13:25:38 <pave1> pavel@denx.de :-).
13:26:07 <iwamatsu__> arisut: Please give me one.
13:26:21 <arisut> ok
13:26:25 <iwamatsu__> thanks
13:27:32 <patersonc> arisut I saw that your config changes were merged. What's next?
13:29:15 <arisut> we still need to enable more boards, architecture and CIP kernels versions with the respective CIP configurations ...
13:30:06 <patersonc> okay
13:30:34 <arisut> is something that I will work on next week
13:31:11 <arisut> current PR was just for organize CIP configurations and starting using CIP configuration
13:31:44 <patersonc> Thank you Arisu-san
13:31:47 <arisut> current PR was just for organize CIP jobs/schedules configurations for KernelCI and starting using the correct CIP Kernel configuration
13:33:08 <jki_> I've just added BBB and M-COM to our reference HW list for 6.12 - we discussed that earlier
13:33:56 <jki_> more on testing?
13:35:00 <jki_> 5
13:35:02 <jki_> 4
13:35:03 <jki_> 3
13:35:05 <jki_> 2
13:35:07 <jki_> 1
13:35:08 <jki_> #topic AOB
13:35:13 <jki_> jrherrera: https://eoss2023.sched.com/event/1LcQW/the-end-of-the-paved-road-maintaining-linux-kernel-44-beyond-lts-ulrich-hecht (was ELC-E, not OSSJ)
13:35:52 <jki_> any other topics to discuss?
13:35:56 <iwamatsu__> I updated wiki.
13:35:57 <iwamatsu__> Just to confirm, is the maintenance period 10 years after the first CIP kernel was released?
13:36:56 <jki_> that's what we did for 6.1
13:37:26 <jki_> and for 5.10 as well - so it makes sense to keep this
13:38:03 <jki_> it is a projected EOL, something possibly to discuss on the last mile if there is need
13:38:14 <iwamatsu__> I understand. Thanks.
13:38:44 <jki_> I've also updated the release cadence of 6.1 in the wiki now
13:38:59 <jki_> 1 / 0.5 as we discussed in the TSC
13:39:19 <iwamatsu__> oh , I forgot it , thanks
13:40:10 <jki_> logistics topic: there is public holiday in Germany next Thursdays
13:40:35 <jki_> I will likely need someone to take over :)
13:41:14 <pave1> I can do that.
13:41:26 <pave1> May 29.
13:41:28 <patersonc> I'll also be off next week
13:41:53 <jki_> right, May 29 - thanks, pavel!
13:42:15 <jki_> other topics for today?
13:42:49 <jki_> 5
13:42:51 <jki_> 4
13:42:53 <jki_> 3
13:42:55 <jki_> 2
13:42:57 <jki_> 1
13:42:59 <jki_> #endmeeting