Thursday, 2025-12-11

*** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Read error: Connection reset by peer)06:11
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip06:24
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)06:29
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip11:56
*** jki <jki!~jki@62.156.206.16> has joined #cip11:58
jkihi!12:00
pave1Hi!12:00
masamihello12:00
jkiI suppose there is some CIP dinner conflict today :)12:01
jkiso, let's do this quickly:12:01
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbot`Meeting started Thu Dec 11 12:01:45 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
jki#topic AI review12:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jkilist was empty again...12:02
jki512:02
jki412:02
jki312:02
jki212:02
jki112:02
jki#topic Kernel maintenance updates12:02
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:02
masamiThis week reported 313 new CVEs and 18 updated CVEs.12:02
pave1I was doing reviews: 6.1.61, and renesas stuff.12:02
pave1And trying to figure out what to do with 4.19-rt (and 6.1-rt).12:02
jkiiwamatsu wrote: I reviewed 6.12.60.12:02
jkianything to add?12:03
jki512:03
jki412:03
jki312:03
jki212:03
jki112:04
jki#topic Kernel release status12:04
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:04
jkitwo are late, 5.10 should pick up soon12:04
pave14.19-rt: I searched other branches to see if someone had to deal with the conflict, but was not successful.12:04
jkiis the issue somewhere visible? maybe my colleague Florian can help with looking around12:05
pave1I believe the best way is to release -rt without the conflicting fix from 4.19-cip, document that, and search for solution after the release.12:05
pave1We have commit 79f919a89c9d06816dbdbbd168fa41d27411a7f9 cgroup: split cgroup_destroy_wq into 3 workqueues12:06
pave1Conflicting with commit 8990cf9c6a65d3d8937db69da5ecd6985c32aa52 cgroups: use simple wait in css_release()12:06
jkilooks not overly critical for production on first sight, indeed12:07
pave1Basically -rt modified code to use different primitive, and -stable split the wq into 3 pieces.12:07
pave1Yep, -stable commit actually has good explanation, it is cgrou + perf_event + net_prio.12:08
jki+ testsuite, de facto12:08
pave1interaction.12:08
pave1Yeah, testing whatever merged version would be an issue, too, as this seems to need quite specific environment.12:09
jkithen let's go for your proposal, I would say12:09
pave1Good :-).12:10
jkithen - move on...12:10
pave16.1-rt is soon, I may need to do 6.1-cip to get a match, but I guess that's okay with everyone.12:10
jkiin general yes, I would just let iwamatsu know as he is not here today12:11
pave1Yep. Also 6.1-rt is month old at this point, if new one appears, that would be great.12:12
jki6.1-stable was late as well, like other stable kernels12:13
jkithere was wave of releases this weekend12:13
pave1jki: There seems to be a trend.12:14
jkiwe need to synchronize then12:14
pave1jki: It looks like -stable team was busy, so they kept releasing 6.12-rt but ignored older ones.12:14
pave1Now they synched up before merge window closing, as it is less busy period  for thm.12:14
pave1I expect this to repeat in future.12:15
jkiask them, then you know for sure :)12:15
jkibut, again, -rt can't release much news of -stable did not release either12:16
pave1This is what happened in the past, too.12:16
jkithen let's synch now and hope it will hold for a while12:17
pave1I believe there was -stable release available, but... I'll need to update, look at versions, and figure things out.12:17
jkithere was none in November for <6.6 IIRC12:17
jkigood - more on this?12:19
jki512:19
jki412:19
jki312:19
jki212:19
jki112:19
jki#topic Kernel testing12:19
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:19
jkitesting team is at dinner, I guess :)12:19
patersoncYep12:20
jkioh!12:20
jkienjoy12:20
patersonc:)12:20
pave1Thanks for 6.17 testing, btw! :-)12:20
patersoncI remembered for once!12:20
patersoncI'll report more testing updates next week12:21
jkithat's fine - thanks!12:21
jkithen let's move on12:21
jki512:22
jki412:22
jki312:22
jki212:22
jki112:22
jki#topic AOB12:22
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:22
jkiany other topic for today?12:22
jki512:23
jki412:23
jki312:23
jki212:23
jki112:23
jki#endmeeting12:23
collab-meetbot`Meeting ended Thu Dec 11 12:23:09 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:23
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-11-12.01.html12:23
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-11-12.01.txt12:23
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-11-12.01.log.html12:23
*** 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:23
jkithanks all!12:23
pave1Thank you!12:23
masamithank you12:23
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:49
*** jki <jki!~jki@62.156.206.16> has quit IRC (Quit: Leaving)12:52
*** biju <biju!~a5122346@81.152.191.146> has joined #cip13:38
*** biju <biju!~a5122346@81.152.191.146> has left #cip (Konversation terminated!)13:38
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has quit IRC (Quit: Konversation terminated!)15:20
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has joined #cip15:20
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Remote host closed the connection)17:45

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