Thursday, 2025-05-22

*** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 272 seconds)01:38
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip05:34
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:50
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)05:55
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection)06:08
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip06:29
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip09:10
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)09:28
*** rajm <rajm!~robert@host-78-151-153-40.as13285.net> has quit IRC (Remote host closed the connection)12:35
*** rajm <rajm!~robert@host-78-151-153-40.as13285.net> has joined #cip12:38
*** jrherrera <jrherrera!~jrherrera@user/jrherrera> has joined #cip12:52
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has joined #cip12:55
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip12:56
*** jki_ <jki_!~jki@195.145.170.148> has joined #cip12:59
jki_hi all12:59
pave1Hi!12:59
masamihello12:59
jrherrerahi!12:59
iwamatsu__hello13:00
arisuthi13:00
patersoncHey13:01
jki_so, let's take off13:01
jki_#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
jki_#topic AI review13:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jki_none recorded, but I should add one for me: "write announcement draft for 6.12-cip"13:02
jki_anything else?13:02
jki_513:02
jki_413:02
jki_313:02
jki_213:02
jki_113:02
jki_#topic Kernel maintenance updates13:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
pave1I was reviewing 6.1.138 and 6.12.30.13:03
masamiThis week reported 100 new CVEs and 2 updated CVEs.13:03
iwamatsu__I reviewed 6.1.137 and 13813:03
jki_anything to add?13:05
jrherreraif it is able to said briefly, how difficult has kernel maintenance of the non-lts branches been?13:05
jki_513:05
jki_you mean 4.4 and now 4.19?13:06
jrherrerayes13:06
jki_ulrich not here today, maybe pavel can comment as well13:07
pave1AFAICT uli is not here today, and he's the one that does that work currently.13:07
pave1Not sure about "how difficult", but good thing is we can take a look at 5.4.X, and only consider patches13:07
jrherreraunfortunate to hear, maybe once Ulrich is back on I can send another comment in the channel13:07
pave1that are applied there.13:08
pave1And those 5.4.X branches are reasonably quiet now.13:08
jki_Ulrich also gave a presentation about 4.4 maintenance at OSSJ in 2023 IIRC13:08
jrherrerathat makes sense actually, it's quite smart. So the older kernels are similar enough so far that back porting is still not too problematic13:09
jrherreraokay! thank you for the answer13:09
jrherrerajki_, can you send me the link in the channel or in PMs after the meeting?13:09
jki_will try to find it, yet13:10
jki_ok, anything else?13:11
jrherrerathat's fine it's not too urgent so we can move on to the next section13:11
jki_513:11
jki_413:11
jki_313:11
jki_213:11
jki_113:11
jki_#topic Kernel release status13:11
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:11
jki_all on track according to our updated schedule13:12
jki_still need to update also the wiki after the 6.12 release13:12
iwamatsu__I can update it.13:12
jki_TIA!13:12
jki_do we keep the reporting script somewhere in git?13:13
jki_I updated mine only locally13:13
jrherreraI'd recommend it13:13
jki_cip-release-term.sh13:13
iwamatsu__Sure.  I will update script.13:13
pave1Yes, it is in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git13:13
pave1The wiki: I guess Ulrich should now be marked as 4.19 maintainer.13:14
jki_right13:14
iwamatsu__OK,13:14
jki_that as well13:14
jki_ok, will send an MR to that repo13:14
jrherreraok13:16
jki_good13:16
jki_then let's move on...13:16
jki_513:16
jki_413:16
jki_313:16
jki_213:16
jki_113:16
jki_#topic Kernel testing13:16
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:16
patersoncHowdy13:16
jrherrerahi!13:17
arisutI'm writing a manual about testing CIP kernel with KernelCI kci-dev13:17
patersoncGreat13:17
arisuthttps://gist.github.com/aliceinwire/4de8692c9e006a2ddf92717fe3aaef0613:17
arisutpratically 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 --tipoftree13:18
arisutwill test linux-6.1.y-cip branch on the last commit with KernelCI13:18
patersoncThanks13:18
arisutadding --watch will wait for results and print on screen13:19
arisutresults will be added to the staging or production dashboard so that can be also checked by browser or using kci-dev results13:19
arisutif anyone want to start trying it, I can give token by email13:20
patersoncyes please13:20
patersoncI 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:21
patersoncWe/TSC also need to finalise this table: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware13:22
arisutpatersonc, thanks13:23
arisutanyone else that want a kci-dev token? just write me a token request by email and I will send it13:24
arisutpave1?13:24
pave1arisut: Yep, I guess one would be useful.13:25
arisutok give me few days and I will send it to you13:25
pave1pavel@denx.de :-).13:25
iwamatsu__arisut: Please give me one.13:26
arisutok13:26
iwamatsu__thanks13:26
patersoncarisut I saw that your config changes were merged. What's next?13:27
arisutwe still need to enable more boards, architecture and CIP kernels versions with the respective CIP configurations ...13:29
patersoncokay13:30
arisutis something that I will work on next week13:30
arisutcurrent PR was just for organize CIP configurations and starting using CIP configuration13:31
patersoncThank you Arisu-san13:31
arisutcurrent PR was just for organize CIP jobs/schedules configurations for KernelCI and starting using the correct CIP Kernel configuration13:31
jki_I've just added BBB and M-COM to our reference HW list for 6.12 - we discussed that earlier13:33
jki_more on testing?13:33
jki_513:35
jki_413:35
jki_313:35
jki_213:35
jki_113:35
jki_#topic AOB13:35
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:35
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
jki_any other topics to discuss?13:35
iwamatsu__I updated wiki.13:35
iwamatsu__Just to confirm, is the maintenance period 10 years after the first CIP kernel was released?13:35
jki_that's what we did for 6.113:36
jki_and for 5.10 as well - so it makes sense to keep this13:37
jki_it is a projected EOL, something possibly to discuss on the last mile if there is need13:38
iwamatsu__I understand. Thanks.13:38
jki_I've also updated the release cadence of 6.1 in the wiki now13:38
jki_1 / 0.5 as we discussed in the TSC13:38
iwamatsu__oh , I forgot it , thanks13:39
jki_logistics topic: there is public holiday in Germany next Thursdays13:40
jki_I will likely need someone to take over :)13:40
pave1I can do that.13:41
pave1May 29.13:41
patersoncI'll also be off next week13:41
jki_right, May 29 - thanks, pavel!13:41
jki_other topics for today?13:42
jki_513:42
jki_413:42
jki_313:42
jki_213:42
jki_113:42
jki_#endmeeting13:42
collab-meetbotMeeting ended Thu May 22 13:42:59 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:42
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-22-13.01.html13:42
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-22-13.01.txt13:42
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-22-13.01.log.html13:42
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"13:42
jki_thanks, folks!13:43
iwamatsu__Thank you13:43
masamithank you13:43
pave1Thank you!13:43
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:43
arisutthx13:44
*** jrherrera <jrherrera!~jrherrera@user/jrherrera> has quit IRC (Ping timeout: 240 seconds)13:46
*** jki_ <jki_!~jki@195.145.170.148> has quit IRC (Quit: Leaving)13:48
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)13:52
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection)17:42
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip17:43
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 248 seconds)18:16

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!