Thursday, 2026-04-16

« Wednesday, 2026-04-15 Index Friday, 2026-04-17 »
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:51
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)05:56
*** frieder <frieder!~frieder@i59F664FE.versanet.de> has joined #cip06:31
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip07:33
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Read error: Connection reset by peer)07:52
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)08:01
*** frieder <frieder!~frieder@i59F664FE.versanet.de> has quit IRC (Remote host closed the connection)11:19
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip11:50
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip11:59
arisuthi12:01
uli_hello12:01
iwamatsuhello12:01
masamihello12:01
patersonchey12:02
*** jki <jki!~jki@62.156.206.18> has joined #cip12:02
jkihi all12:02
iwamatsuhi12:02
jkiok, already late12:02
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbot`Meeting started Thu Apr 16 12:02:49 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-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbot`The 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
jkinone12:03
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
masamiThis week reported 16 new CVEs and 12 updated CVEs.12:03
uli_pushed 4.19, will do 4.4 next12:03
iwamatsuI am revieweing 6.12.8012:03
pave1I was reviewing 6.12.81, .8212:04
jkianything else?12:04
jki512:05
jki412:05
jki312:05
jki212:05
jki112:05
jki#topic Kernel release status12:05
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:05
jki4.4 is due, will come soon as Uli just said12:05
jki4.19-rt: what is now the conclusion?12:05
pave1Lets do a release next12:06
pave1month after 4.19-cip is released.12:06
pave1That way code is not too old12:06
pave1and we don't have too many releases.12:07
jkiyou mean do a release for -rt soon after the next regular 4.19-cip release?12:07
jkiyeah, that is the point of this old kernels12:07
pave1yes.12:07
jkiok, noted12:07
jkianything else on releases?12:08
jki512:08
jki412:08
jki312:08
jki212:08
jki112:08
jki#topic Kernel testing12:08
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:08
patersoncHey.12:08
patersoncWe still have some boards offline in the SIemens lab12:09
jkiwhich Siemens lab?12:09
patersoncAlthough the lab is at least back online now since yesterday12:09
patersonc3 offline in Prague. 1 in Munich12:09
jkiwill clarify12:09
patersoncThanks12:10
patersoncNothing else to report from my side12:10
jkipatersonc: do you have email notifcation options for the worker or device states?12:11
patersoncEmails get sent to cip-testing-results@lists.cip-project.org when a healthcheck fails, but they probably get lost in a lot of traffic12:12
jkiyeah, only state changes, and that for boards someone is responsible for12:12
jkibtw, the riscv board in the MUC lab is only planned, was never brought online12:13
patersoncGotcha12:14
jkiwe were considering to enable it with image support (mtda) but that work got delayed12:14
jkiand did "riscv" mean "beaglev"? you once created that, patersonc12:15
jkithe beaglev-fire are a different device type12:15
patersoncNo. Beaglevs are here: https://lava.ciplatform.org/scheduler/device_type/beaglev-fire12:15
jkiexactly12:16
jkiI have a fire with my, currently not wired up with a lab, that could join the pool once we have time - and need12:16
jkior we have an mtda setup to run full images on it12:17
patersoncThat would be more useful me thinks12:17
jkithen I guess that generic "riscv" device can go again - or keep it and rename it?12:18
patersoncIt would probably be better to be more specific12:18
jkiok, will talk to Quirin about that one12:20
jkianything else on testing?12:20
patersoncNot from me12:20
jkithen let's move on...12:21
arisutno12:21
jki512:21
jki412:21
jki312:21
jki212:21
jki112:21
jki#topic AOB12:21
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:21
jkiuli_: thanks for reminding of Embedded Recipes!12:22
uli_np12:22
jkiwill not go there as well, not sure who else plans that12:22
jkisome tickets still left12:22
uli_i'm still waiting for yoshi's final approval, though. but i guess the conditions are met.12:23
jkiwill ping him again12:26
jkiok, other topics for today?12:26
uli_thx12:26
jki512:26
jki412:26
jki312:26
jki212:26
jki112:26
jki#endmeeting12:26
collab-meetbot`Meeting ended Thu Apr 16 12:26:49 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:26
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-16-12.02.html12:26
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-16-12.02.txt12:26
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-16-12.02.log.html12:26
*** 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:26
jkithanks!12:26
pave1Thank you!12:26
iwamatsuThank you12:26
uli_thank you12:26
masamithank you.12:27
*** frieder <frieder!~frieder@i59F664FE.versanet.de> has joined #cip12:27
patersoncCheers12:27
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:45
*** jki <jki!~jki@62.156.206.18> has quit IRC (Quit: Leaving)12:52
*** frieder <frieder!~frieder@i59F664FE.versanet.de> has quit IRC (Read error: Connection reset by peer)15:02
*** vigneshr <vigneshr!uid375618@user/vigneshr> has quit IRC (Quit: Connection closed for inactivity)15:14
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has joined #cip16:09
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds)16:57
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has joined #cip16:57
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)17:35
« Wednesday, 2026-04-15 Index Friday, 2026-04-17 »

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