Thursday, 2024-10-24

« Wednesday, 2024-10-23 Index Friday, 2024-10-25 »
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Quit: quit)01:00
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip01:02
*** cbeznea <cbeznea!~cbeznea@82.78.167.23> has quit IRC (Read error: Connection reset by peer)01:04
*** cbeznea <cbeznea!~cbeznea@82.78.167.23> has joined #cip01:05
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Read error: Connection reset by peer)01:15
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip01:18
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:32
*** cbeznea <cbeznea!~cbeznea@82.78.167.23> has quit IRC (Quit: Leaving)08:12
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 252 seconds)11:49
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.46> has joined #cip11:50
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.46> has quit IRC (Ping timeout: 252 seconds)11:55
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip11:56
*** ironfoot_ <ironfoot_!~pedroalva@user/ironfoot> has joined #cip12:47
*** ironfoot <ironfoot!~pedroalva@user/ironfoot> has quit IRC (Read error: Connection reset by peer)12:47
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:59
*** jki <jki!~jki@46.128.82.72> has joined #cip13:03
jkihi all, sorry for the delay13:03
arisuthello13:03
patersoncHello13:03
masamihi13:03
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:c2c6:9187:2f03:5298> has joined #cip13:04
ulihello13:04
iwamatsu__hello13:04
jki#startmeeting CIP IRC weekly meeting13:04
collab-meetbot`Meeting started Thu Oct 24 13:04:28 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:04
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:04
jki#topic AI review13:04
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:04
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:04
jkimoved to the back again over vacation...13:04
jkiI haven't seen other AIs from last week, right?13:05
jki513:05
jki413:05
jki313:05
jki213:05
pave1No new ai.13:05
jki113:05
pave1AIs.13:05
jki#topic Kernel maintenance updates13:05
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:05
masamiThis week reported 384 new CVEs and 37 updated CVEs.13:05
pave1I'm reviewing 6.1.113 / 114.13:05
ulii reviewed 6.1.113 and prepared 4.413:05
iwamatsu__I am reviewing 6.1.11413:06
jkidid we already clarify who is handling the next 4.4, under which conditions?13:07
pave1Not really, this sounds like a good place.13:07
ulilooking at the timing, i think it might even be best to push it back until i come back from japan on nov 14 (it's due nov 9)13:07
pave1I'd say that's best plan.13:08
jkiyes, if there is nothing surprisingly urgent showing up, that is fine13:08
jkigood, check-mark13:08
jkianything else?13:09
jki513:09
jki413:09
jki313:09
jki213:09
jki113:09
jki#topic Kernel release status13:09
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:09
jkiall are green right now13:09
jkianything to add?13:09
pave1I thought ... 4.19-cip-rt is now.13:10
jkiuups, indeed13:10
jkiwas color-blind13:10
jkiactually, not -rt, vanilla 4.1913:10
iwamatsu__I will working it.13:11
iwamatsu__I am working it.13:11
jkiok, great13:11
pave1We don't have corresponding 4.19-rt, so I guess its a bit more waiting and then asking for 4.19-rt.13:11
jkilimit date: Sat Nov 23 10:34:04 AM UTC 202413:11
jkithat's for 4.19-rt13:11
jkino?13:11
pave1Oops, yes, you are right. I made mistake in my notes, will fix.13:12
jkiokay...13:12
jkithen let's move on13:12
jki513:13
jki413:13
jki313:13
jki213:13
jki113:13
jki#topic Kernel testing13:13
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:13
arisutno updates from me13:13
jkiseems lava master if fine again, right?13:13
jkicurrently no issues in testing?13:13
patersoncSeems okay at the moment13:14
jkigreat13:14
patersonctouch wood13:14
jkiand no intruder had to be kicked out ;)13:14
patersoncAnd I got the Renesas lab back online this morning13:14
jkiother testing topics?13:15
jki513:15
jki413:15
jki313:15
jki213:15
jki113:15
jki#topic AOB13:16
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:16
jkinext week is E-TSC, again13:16
jkianything we should bring up as kernel WG?13:16
pave1I can't think of anything.13:16
jkieffort planning 2025 - I'm sure we will be asked again13:17
pave1beggining of 2025 will be hard, yes.13:17
jkiwe are currently planning with same contractural efforts13:18
pave1I don't expect to hit the contracted hours this year.13:18
pave1That may change in 2025 I guess.13:18
jkiok, that is important input13:18
jkido you expect to overshoot in 25?13:19
pave1No idea ATM, really. I'd expect that no.13:19
jkiwe can still react over the year, to a certain degree13:19
pave1We are currently doing a lot of -stable reviewing.13:19
jkiwhich is good13:20
jkido you mean we would have to reduce that for the sake of "own" work?13:20
pave1I guess that we can do less over the "surge" expected in 2025, without great consequences.13:20
pave1I'm not sure if we'll have to reduce that,13:21
jkiwell, we will start with the next CIP kernel, and that will see a lot of updates initially13:21
pave1but I believe we can reduce that if needed.13:21
jkiand there will be the 4.19 take-over, right?13:21
pave1Yes, 4.19 takeover and new kernel.13:21
jkifolks, you doing the real work, just tell me early enough when the load goes up too much13:22
pave1Will do, but it is hard to estimate at the moment :-).13:22
jkiwe don't want interruptions, we want time to be able to react13:22
jkiyes, understood13:23
iwamatsu__OK13:23
pave1Currently, there's time to review patches that are not affecting any known CIP config.13:23
pave1That's first on the list ;-).13:23
jkisure13:23
jkiother businesses for today?13:24
patersoncI guess there's potential for a wider config list for CIP to maintain if requests by any new members to the project. But obviously that cannot be predicted/estimated at this point. But perhaps worth considering13:24
patersoncs/requests/requested13:25
jkiright13:25
jkibut maybe we could also ask a potential new member for getting involved ;)13:26
patersoncTrue!13:26
pave1Right ;-).13:26
jkiideally also on testing...13:26
patersoncyep13:27
pave1There's also possibility to ask for pruning of configs. We have udf/btrfs on, bunch of scsi, etc.13:27
jkisure13:27
jkianything else for today?13:28
jki513:28
jki413:28
jki313:28
jki213:28
pave1oh.13:28
jkiyes?13:28
pave1E-tsc. That's like 4 am utc, right13:28
pave1?13:28
patersoncSomething like that13:29
jkiyes, but I will not be up that early as well13:29
pave1So, no big deal if I can't make it? :-)13:29
jkiI hope Yoshi is not scheduling the kernel into our night13:29
patersoncWe can move the kernel team bit to the end?13:29
jkiyes, please13:29
jki6 am should work13:30
jkimaybe even 5 - we have the time shift next weekend13:30
patersoncI'll make sure it's at the end during the meeting, or we can ask before hand if Yoshi-san publishes an agenda (I haven't seen one yet)13:31
jkiyep, thanks13:31
jkiok... let's try closing again13:31
jki513:32
jki413:32
jki313:32
jki213:32
jki113:32
jki#endmeeting13:32
collab-meetbot`Meeting ended Thu Oct 24 13:32:11 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:32
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-24-13.04.html13:32
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-24-13.04.txt13:32
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/10/cip.2024-10-24-13.04.log.html13:32
*** 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:32
jkithanks, folks!13:32
ulithanks13:32
pave1Thank you!13:32
iwamatsu__thank you13:32
masamithank you13:32
*** jki <jki!~jki@46.128.82.72> has quit IRC (Quit: Leaving)13:32
arisutthanks13:35
patersoncthanks13:37
patersoncSee you in Tokyo next week :)13:37
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:17
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)15:45
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:c2c6:9187:2f03:5298> has quit IRC (Quit: Client closed)16:38
« Wednesday, 2024-10-23 Index Friday, 2024-10-25 »

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