| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip | 00:03 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer) | 01:37 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip | 01:38 | |
| *** hiromotai <hiromotai!~Hirotaka@2404:7a80:37e0:c500:c277:4720:7d1:1ac2> has joined #cip | 06:51 | |
| *** hiromotai <hiromotai!~Hirotaka@2404:7a80:37e0:c500:c277:4720:7d1:1ac2> has quit IRC (Client Quit) | 06:52 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 06:54 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 07:04 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 08:08 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 08:13 | |
| *** frieder <frieder!~frieder@89.244.121.53> has joined #cip | 08:19 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds) | 08:25 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 08:26 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:11 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 09:14 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:16 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 09:18 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:52 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 09:55 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 10:44 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 10:44 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 11:00 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 11:01 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 256 seconds) | 11:19 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 11:20 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Read error: Connection reset by peer) | 11:24 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 11:24 | |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip | 11:53 | |
| *** jki <jki!~jki@62.156.206.55> has joined #cip | 11:58 | |
| jki | hi everyone | 11:59 |
|---|---|---|
| pave1 | Hi! | 11:59 |
| masami | hi | 12:00 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:00 | |
| patersonc | Hello | 12:01 |
| jki | time to start | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
| collab-meetbot` | Meeting started Thu Feb 5 12:01:29 2026 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 review | 12:01 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | empty | 12:01 |
| iwamatsu__ | hello | 12:01 |
| jki | 5 | 12:01 |
| jki | 4 | 12:01 |
| jki | 3 | 12:01 |
| jki | 2 | 12:01 |
| jki | 1 | 12:01 |
| jki | #topic Kernel maintenance updates | 12:01 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| masami | This week reported 116 new CVEs and 16 updated CVEs. | 12:02 |
| pave1 | I was reviewing 6.12.67 and .68 | 12:02 |
| iwamatsu__ | I reviewed 6.12.67 | 12:02 |
| jki | further topics? | 12:04 |
| jki | 5 | 12:04 |
| jki | 4 | 12:04 |
| jki | 3 | 12:04 |
| jki | 2 | 12:04 |
| jki | 1 | 12:04 |
| jki | #topic Kernel release status | 12:04 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:04 | |
| pave1 | 4.19-rt was released. | 12:04 |
| jki | thanks! | 12:05 |
| jki | nicely aligned again | 12:05 |
| jki | news from 6.1-rt? | 12:05 |
| pave1 | Currently I'm working on 6.1-rt. -rt is done, but -rt-rebase is going to be a bit tricky | 12:05 |
| pave1 | and it will make next -rt-rebase tricky. | 12:05 |
| jki | what is particularly tricky about it? | 12:06 |
| pave1 | So ... there's 6.1 -- stable -- rt -- cip | 12:07 |
| pave1 | We have cip on top of rt, but now cip and rt is on different stable kernels. | 12:07 |
| pave1 | So I'll need to invent a rt "release" and put cip on top of that. | 12:08 |
| pave1 | And next time I'll try to do 6.1-rt, tag will not exist. | 12:08 |
| pave1 | Fortunately -rt is easy and I can compare the trees, which should tell me if something went wrong. | 12:08 |
| jki | maybe you can offer your rt work to stable-rt, and Clark will pick it up for a release? | 12:09 |
| jki | would be nice anyway | 12:09 |
| pave1 | I assume he has scripts he can just follow. | 12:10 |
| jki | anyway, the information that rebasing is straightforward may help that he actually starts this | 12:10 |
| pave1 | There should be no "real" work in the rebasing, but I need to document the steps for later use and not break something in the process. | 12:11 |
| jki | in the end, we also want upstream stable-rt to proceed, at least as long as stable exists for 6.1 | 12:11 |
| pave1 | Yes, stable-rt is good for us. | 12:12 |
| jki | then continue to motivate them to release ;) | 12:13 |
| pave1 | Yeah, I'm not sure I'm right person for that :-) | 12:13 |
| jki | is your branch somewhere visible already? Then I could use it to talk to Clark again | 12:15 |
| pave1 | I'm currently testing it at https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2307585171 | 12:15 |
| jki | and the code is where? | 12:16 |
| pave1 | Let me get to successful tests before pushing it to -cip. | 12:16 |
| jki | ok, just let me know | 12:17 |
| pave1 | Ok. I'll add some kind of tag when creating -rebase tree; that's what will be usefull for outside world, anyway. | 12:17 |
| jki | ok, rest of the releases are on track - anything to add? | 12:17 |
| jki | 5 | 12:18 |
| jki | 4 | 12:18 |
| jki | 3 | 12:18 |
| jki | 2 | 12:18 |
| jki | 1 | 12:18 |
| jki | #topic Kernel testing | 12:18 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:18 | |
| patersonc | The KernelCI PR adding beaglev-fire support was merged, but not pushed to production yet | 12:19 |
| pave1 | So... bbb is still acting up, as can be seen in https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2307585171 | 12:19 |
| patersonc | Thanks Pavel | 12:19 |
| pave1 | (The other 3 failures -- should I just hit retry?) | 12:21 |
| patersonc | Both of the ipc227e failures seem to be caused by the tests taking too long and it timing out | 12:21 |
| patersonc | One took ages to boot. The other seemed to stop doing anything after the CVE tests were run | 12:23 |
| jki | bbb: "bootserver=192.168.175.254, rootserver=192.168.0.2, rootpath=" and "VFS: Unable to mount root fs via NFS." | 12:23 |
| jki | that empty rootpath looks suspicious | 12:24 |
| jki | a non-empty one was passed via cmdline, though | 12:24 |
| jki | who's operating this? | 12:24 |
| patersonc | This bbb device doesn't seem happy for aany testing: https://lava.ciplatform.org/scheduler/device/beaglebone | 12:25 |
| patersonc | Same/similar tests on another bbb seem okay: https://lava.ciplatform.org/scheduler/device/bbb-iwamatsu-01 | 12:25 |
| jki | is it always the one from our Prague lab? | 12:25 |
| jki | then I will ping Pasquale on this | 12:26 |
| patersonc | The device dictionary is missing "{% set extra_nfsroot_args = ',vers=3' + extra_nfsroot_args|default('') %}" | 12:26 |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Read error: Connection reset by peer) | 12:26 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 12:26 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Client Quit) | 12:28 | |
| patersonc | Hopefully that'll fix the bbb issue Pavel. We'll have to look at ipc test timeouts later | 12:28 |
| jki | who can change that? | 12:28 |
| patersonc | rzfive failure was random serial failure, fix with rerun | 12:28 |
| jki | I informed Pasquale in any case | 12:28 |
| patersonc | jki: Pasqaule | 12:28 |
| jki | ok | 12:28 |
| pave1 | Ok, I'll hit rerun on everything -- I believe it will pass, so save the "bad" results if you want them. | 12:29 |
| patersonc | okay | 12:29 |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 12:30 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 12:30 | |
| jki | more on testing? | 12:30 |
| arisut | working on kci-dev | 12:31 |
| arisut | but no new updates | 12:31 |
| patersonc | Nothing else from me | 12:32 |
| jki | then let's move on | 12:33 |
| jki | 5 | 12:33 |
| jki | 4 | 12:33 |
| jki | 3 | 12:33 |
| jki | 2 | 12:33 |
| jki | 1 | 12:33 |
| jki | #topic AOB | 12:33 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:33 | |
| pave1 | I'll be travelling next week. | 12:33 |
| jki | I have one topic: did we document feature / board support backporting rules anywhere? | 12:34 |
| pave1 | Hopefully with my notebook this time :-) | 12:34 |
| jki | I scanned https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance for it but didn't find a lot | 12:34 |
| jki | background: will have a call with a CIP-interested party on this particular topic tomorrow | 12:35 |
| pave1 | I am not sure if we have explicit rules somewheer | 12:35 |
| pave1 | AFAICT the rules are: | 12:36 |
| patersonc | Isn't that what the "Suitable changes" section is? | 12:36 |
| pave1 | a) It must be in mainline, or mainline must have different fix for the same bug | 12:36 |
| pave1 | b) If it is in older-cip, it must be in all newer-cip trees | 12:37 |
| jki | yeah, but board enabling is not really "bug" | 12:37 |
| pave1 | c) If it touches common code... well... we are more careful | 12:38 |
| jki | maybe you (maintainers) could check the wiki again and maybe augment things a bit for the feature backporting topic | 12:38 |
| jki | I already explained in an email that we do not accept complete subsys refactorings as backports | 12:38 |
| jki | due to testability issues already | 12:39 |
| pave1 | yep. | 12:39 |
| pave1 | Basically we were going by "does this look ok" to now. | 12:39 |
| jki | maybe you also remember some good examples from the past? | 12:39 |
| jki | to give people an impression | 12:40 |
| pave1 | I really do not want to see "here's intrusive series, but it meets rules, so apply it". | 12:40 |
| pave1 | Oh and | 12:40 |
| pave1 | d) series should be less than 30 or so patches each. | 12:40 |
| jki | putting a "CIP maintainers have last word" there is a rule to prevent that? | 12:40 |
| pave1 | Renesas is doing quite good job pushing the patches. There are numerous examples on the mailing list. | 12:41 |
| jki | I also meant examples that may have required some adjustments, a second round | 12:42 |
| pave1 | Concretely "Biju Das" knows how to submit patches. | 12:42 |
| pave1 | There are not many of those. | 12:42 |
| pave1 | Ok, there's | 12:42 |
| pave1 | e) if it is applicable to -stable, it should go through -stable | 12:42 |
| pave1 | We asked for explanations when they touched common code. | 12:43 |
| pave1 | Recently MSTOP patches went up to v3, because we were trying to push them to drivers-only solution but that turned out to be too intrusive. | 12:44 |
| pave1 | And sometimes we get patches that don't work or are not signed-off or something. Fortunately not too common. | 12:44 |
| jki | ok, will assembly my replies from this | 12:45 |
| pave1 | "If you are not modifying common code, you can expect about 20 patches a week being merged if they meet the criteria above" :-) | 12:45 |
| jki | would still be nice to have a bit more written in the wiki | 12:45 |
| jki | any other businesses for today? | 12:46 |
| jki | 5 | 12:47 |
| jki | 4 | 12:47 |
| jki | 3 | 12:47 |
| jki | 2 | 12:47 |
| jki | 1 | 12:47 |
| jki | #endmeeting | 12:47 |
| collab-meetbot` | Meeting ended Thu Feb 5 12:47:15 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:47 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/02/cip.2026-02-05-12.01.html | 12:47 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/02/cip.2026-02-05-12.01.txt | 12:47 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/02/cip.2026-02-05-12.01.log.html | 12:47 |
| *** 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:47 | |
| jki | thanks! | 12:47 |
| pave1 | Thank you! | 12:47 |
| iwamatsu__ | Thank you. | 12:47 |
| masami | thank you | 12:47 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 12:47 | |
| *** jki <jki!~jki@62.156.206.55> has quit IRC (Quit: Leaving) | 12:47 | |
| arisut | thanks | 12:51 |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:51 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 13:51 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 13:51 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 14:02 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 14:02 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer) | 15:10 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 15:30 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 15:30 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds) | 15:45 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 15:48 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 15:54 | |
| *** frieder <frieder!~frieder@89.244.121.53> has quit IRC (Remote host closed the connection) | 16:27 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip | 17:39 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 18:10 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 22:34 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!