Thursday, 2026-01-08

*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer)05:29
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip05:36
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip06:52
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)07:02
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip10:02
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)10:17
*** sskartheekadivi <sskartheekadivi!~sskarthee@122.171.20.247> has joined #cip10:47
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip11:53
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip11:54
*** jki <jki!~jki@62.156.206.20> has joined #cip12:00
jkihi all12:01
uli_hello12:01
iwamatsu__hello12:01
masamihello12:01
pave1Hi!12:01
arisut_hi12:01
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbotMeeting started Thu Jan  8 12:02:42 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
jki#topic AI review12:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
jkinone on the list12:02
jki512:03
jki412:03
jki312:03
jki212:03
jki112:03
jki#topic Kernel maintenance updates12:03
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:03
uli_i pushed 4.19 and 4.412:03
pave1I did reviews: 6.1.63 and .64, and a lot of Renesas patches.12:03
iwamatsu__I reviewed 6.12.62 and 63,and  renesas patches.12:04
pave1We are down to MSTOP + I3C to review now.12:04
masamiThis week reported 16 new CVEs and 0 updated CVEs.12:04
iwamatsu__pave1: about MSTOP patches, I am reviewing12:04
pave1Big change with me is that Denx is shutting down, and Nabla is replacing it.12:04
pave1...so please update my email with pavel@nabladev.com.12:05
pave1iwamatsu: Thanks!12:05
pave1iwamatsu: There's v1 and v2 of the MSTOP patches. Last time I looked, v1 looked like better approach.12:05
iwamatsu__Pave1: I see. I will check v1 too.12:06
jkii had to debug two stable regressions these days as well12:08
*** jki <jki!~jki@62.156.206.20> has quit IRC (Ping timeout: 264 seconds)12:13
pave1Ouch. It seems like jki has connection problem.12:13
iwamatsu__hmm12:15
iwamatsu__move to next topic?12:15
pave1I guess so. We can revisit if he reappears.12:16
pave1512:16
pave1412:16
pave1312:16
pave1212:16
pave1112:16
pave1*** topic: Kernel release status12:17
*** jki <jki!~jki@195.145.170.151> has joined #cip12:17
jkistill there?12:17
pave1Still here. We are ready12:17
jkiI'm facing client issues12:17
pave1to move to kernel release status if that's ok.12:17
jkiyes, I tried12:17
jkiretrying12:17
jki#topic Kernel maintenance updates12:18
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:18
jkiok, now it worked12:18
pave1Good :-)12:18
jkilot of delayed -rt releases12:18
pave14.4-rt is due. Uli released kernels so I should be able to do it now.12:18
*** jki <jki!~jki@195.145.170.151> has quit IRC (Remote host closed the connection)12:18
pave1I'll check the dates on rest.12:19
*** jki <jki!~jki@195.145.170.151> has joined #cip12:19
jkilost the client again12:20
jkiso, plans for 5.10-rt and 6.1-rt as well?12:20
jkipavel: ?12:21
pave1I'll check the dates and do the releases.12:21
iwamatsu__5.10. y-cip-rt seems ready for release.12:21
jkiboth are due12:21
pave1So I'll do the releases :-)12:22
jkiok, perfect12:22
jkianything else regarding releases?12:22
jki512:22
jki412:22
jki312:23
jki212:23
jki112:23
jki#topic Kernel testing12:23
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:23
patersoncI'm travelling at the moment so a limited update from me... We now have a couple of beaglev-fire boards online in our lava setup. New TI boards should be shipping next week.12:23
patersoncSetup of new TI lab is just starting12:23
pave1Tests on mcom are failing. I'm ignoring the failures for now.12:24
arisut_from me not so much ether, working on a new release for kci-dev and added deb packages on new releases12:24
arisut_also working on making kci-dev a library for been integrated with other tools12:24
jkipavel: which tests?12:24
patersoncSeem to have a lot of boot issues in kernelCI, e.g. G1M, but I haven't investigated further yet.12:24
iwamatsu__One reason is that there is only one mcom device.12:24
patersoncMcom board is offline12:24
pave1All tests, afaict: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2250334613 is an example12:25
jkiah, I see12:25
pave1It says 0 available boards, so not a "real" failure.12:25
arisut_will be possible to use kci-dev both as stand alone client tool and as library12:25
jkilet me ping Pasquale12:25
patersoncarisut_: nice12:25
patersoncWe need to get all the mcom boards merged under the same device-type name12:26
patersoncThen we'd have 312:26
jkiwhere is the 3rd?12:28
jkithe mcom-mtda is differently configured12:29
patersoncCan it run the same s/w though?12:29
jkiI just started discussion with colleagues here how to scale out mtda setups, and then also make sure that we can still run normal kernelci12:29
patersoncOkay great. Thanks Jan12:30
patersoncI thought we had two mtda devices in the lab, looks like only 1 now12:31
jkistill only one12:31
jkithe second one was/is planned for Prague12:31
jkibut still on the todo list12:31
jkimore on testing?12:33
jki512:33
jki412:33
jki312:33
jki212:33
jki112:33
jki#topic AOB12:33
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:33
jkiI won't be able to run next week's meeting12:34
jkiwho can take over?12:34
pave1I can do it.12:34
jkipavel: TIA!12:34
pave1AFAICT there's Zoom meeting on 13th?12:34
pave1TSC?12:34
jkithat is also true - I was referring to the irc meeting12:35
jki(but I will likely be absent for the TSC as well)12:35
pave1I know. I may or may not be able to make it on 13th.12:35
pave1...so apologies in advance if I can't make it.12:36
iwamatsu__If that happens, I'll do it.12:37
pave1I meant -- I can make it to irc on 15th. Not sure I can make it to Zoom on 13th.12:38
jkiI think we can skip the kernel WG on the 13th, not much news I guess12:38
jkianything else for today?12:39
jki512:40
jki412:40
jki312:40
jki212:40
jki112:40
jki#endmeeting12:40
collab-meetbotMeeting ended Thu Jan  8 12:40:24 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:40
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-08-12.02.html12:40
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-08-12.02.txt12:40
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-08-12.02.log.html12:40
*** 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/"12:40
jkithanks all!12:40
pave1Thank you!12:40
uli_thanks12:40
iwamatsu__Thank you12:40
masamithank you12:40
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:40
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)12:42
*** jki <jki!~jki@195.145.170.151> has quit IRC (Remote host closed the connection)13:02
*** sskartheekadivi_ <sskartheekadivi_!~sskarthee@122.171.20.247> has joined #cip17:43
*** sskartheekadivi <sskartheekadivi!~sskarthee@122.171.20.247> has quit IRC (Ping timeout: 240 seconds)17:43
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has quit IRC (Quit: Konversation terminated!)22:59
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has joined #cip22:59
*** sskartheekadivi_ <sskartheekadivi_!~sskarthee@122.171.20.247> has quit IRC (Ping timeout: 246 seconds)23:28

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