| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Ping timeout: 252 seconds) | 00:31 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has joined #cip | 00:32 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Ping timeout: 268 seconds) | 00:43 | |
| *** monstr <monstr!~monstr@nat-108.starnet.cz> has joined #cip | 05:04 | |
| *** monstr <monstr!~monstr@nat-108.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 05:09 | |
| *** 020ABITO9 <020ABITO9!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has joined #cip | 06:10 | |
| *** 020ABITO9 <020ABITO9!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 06:14 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has joined #cip | 06:17 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds) | 06:45 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has joined #cip | 06:45 | |
| *** monstr <monstr!~monstr@nat-108.starnet.cz> has joined #cip | 09:15 | |
| *** monstr <monstr!~monstr@nat-108.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 09:41 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has joined #cip | 12:35 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Ping timeout: 276 seconds) | 12:37 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:53 | |
| *** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has joined #cip | 12:53 | |
| *** jki <jki!~jki@195.145.170.148> has joined #cip | 12:57 | |
| jki | hi all | 12:59 |
|---|---|---|
| uli_ | hello | 12:59 |
| patersonc | hey | 13:01 |
| jki | small round today? | 13:01 |
| jki | well, let's slowly start :) | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot` | Meeting started Thu Jul 10 13:02:03 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:02 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | #topic AI review | 13:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| iwamatsu__ | hello | 13:02 |
| jki | none on my list | 13:02 |
| jki | 5 | 13:02 |
| jki | 4 | 13:02 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #topic Kernel maintenance updates | 13:02 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| uli_ | still working on 4.19, it's a big one | 13:02 |
| masami | This week reported 170 new CVEs and 9 updated CVEs. | 13:02 |
| iwamatsu__ | I reviewed 6.12.35 and 36. | 13:03 |
| pave1 | I'm reviewing 6.12.35 and .36. | 13:03 |
| jki | anything to add? | 13:04 |
| jki | 5 | 13:05 |
| jki | 4 | 13:05 |
| jki | 3 | 13:05 |
| jki | 2 | 13:05 |
| jki | 1 | 13:05 |
| jki | #topic Kernel release status | 13:05 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| jki | 6.1-rt is late - waiting for upstream? | 13:06 |
| iwamatsu__ | I am preparing now. I am going to release tomorrow. | 13:06 |
| pave1 | Not really, more confusion on my part. | 13:06 |
| iwamatsu__ | I am preparing now. I am going to release tomorrow. > 6.12.y-cip | 13:06 |
| jki | ok, assumed so :) | 13:07 |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Read error: Connection reset by peer) | 13:07 | |
| jki | pavel: you just missed the deadline? | 13:07 |
| jki | do we have a suitable base for 6.1-rt? | 13:07 |
| pave1 | I'll need to take a look. | 13:07 |
| jki | ok | 13:07 |
| pave1 | As cadence changed from 1 to two months, I simply added 2 months to the date. | 13:08 |
| pave1 | Which ... was not correct thing to do :-) | 13:08 |
| jki | we have a common script :) | 13:08 |
| pave1 | and that's good because it catches errors. I'm keeping whiteboard in local file. | 13:08 |
| jki | anything else on releases? | 13:09 |
| jki | 5 | 13:09 |
| jki | 4 | 13:09 |
| jki | 3 | 13:09 |
| jki | 2 | 13:09 |
| jki | 1 | 13:09 |
| jki | #topic Kernel testing | 13:09 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:09 | |
| arisut | I finally got cip configurations on KernelCI | 13:10 |
| patersonc | Nothing from me | 13:10 |
| arisut | we had a problem with identical jobs names that was blocking the cip configurations introduction but as been fixed | 13:10 |
| patersonc | Good | 13:11 |
| arisut | currently I'm adding lab-cip boards to KernelCI | 13:11 |
| patersonc | Thanks! | 13:11 |
| jki | nice | 13:11 |
| jki | btw, the configs we have in x.y-cip vs. those in regular branches in cip-kernel-configs are not in sync | 13:12 |
| jki | is that a problem? | 13:12 |
| arisut | what do you mean by x.y-cip configuration ? | 13:12 |
| arisut | the one inside the cip kernel repo? | 13:13 |
| arisut | we are using cip-kernel-configs | 13:13 |
| jki | in the cip-kernel-config repo | 13:13 |
| jki | we have branches for every kernel there | 13:13 |
| arisut | yes | 13:13 |
| jki | but feature maintance only happens against the -cip branches | 13:13 |
| jki | at least in most cases | 13:14 |
| arisut | you mean dose not happen in -cip-rt branches for example ? | 13:15 |
| arisut | does | 13:15 |
| jki | also | 13:15 |
| arisut | or in .y version | 13:15 |
| jki | for focus is on -cip for features | 13:16 |
| arisut | currently I'm using only the -cip branches | 13:16 |
| arisut | afair | 13:16 |
| jki | -rt is normally added via snippet | 13:16 |
| jki | okay, that would be up-to-date | 13:16 |
| arisut | maybe -cip-rt also | 13:16 |
| jki | I never touched a cip-rt for feature extensions, but that is because we use the rt snippet for enabling RT | 13:17 |
| arisut | yes also cip-rt | 13:17 |
| arisut | ok | 13:17 |
| arisut | is that a problem? | 13:17 |
| jki | I was just wondering if it affects our testing efforst negatively if we add feature X to .y-cip but not to .y+1 or so | 13:18 |
| jki | configs for regular stable kernels are taken as snapshots from the -cip kernels when we add the stable ones, right? | 13:19 |
| jki | no more updates afterwards | 13:19 |
| pave1 | Yeah, making sure features we use are tested in newer stable kernels would make some sense. | 13:19 |
| arisut | maybe we could loose regression bugs on such features ? | 13:19 |
| jki | we currently only spot regressions for recently added features if related patches land in -cip | 13:20 |
| jki | if we want to change that, we likely need to automate forward-porting of feature additions | 13:20 |
| jki | similar to the cip_merged config generation | 13:20 |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Ping timeout: 265 seconds) | 13:21 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has joined #cip | 13:22 | |
| jki | well, will need someone to implement that... | 13:22 |
| pave1 | Or we can ask people submitting new features to do that. | 13:22 |
| pave1 | :-). | 13:22 |
| jki | manual checks don't work | 13:23 |
| pave1 | They may be good enough. | 13:23 |
| jki | process is already complicated enough, just went through this | 13:23 |
| pave1 | There will be manual component as submitter knows which kernel to enable feature on. | 13:23 |
| jki | ...which CIP kernel | 13:24 |
| jki | that is what people care about in CIP | 13:24 |
| patersonc | Having different config versions for every kernel kernel version is a pain. But I guess a single defconfig wouldn't work either because different kernel versions have new features we may want to test? | 13:24 |
| pave1 | Aha, I thought that idea would be: | 13:24 |
| pave1 | when "shiny cat" feature is ported from 6.16 to 6.1-cip | 13:24 |
| pave1 | we also need to enable 'shiny cat" in 6.12-cip and 6.16-stable test configurations. | 13:25 |
| pave1 | (and 6.17-stable and 6.18-stable) so that we see regressions early. | 13:25 |
| jki | and that should be auto-checked at least | 13:25 |
| jki | or it will constantly be forgotten | 13:25 |
| jki | better would be auto-generation of the stable configs | 13:26 |
| jki | so that -cip ones remain the only base | 13:26 |
| jki | just like no one is supposed to touch the merged configs manually anymore | 13:26 |
| jki | ok - more on testing? or configs? :) | 13:28 |
| jki | 4 | 13:28 |
| jki | 4 | 13:28 |
| jki | 3 | 13:28 |
| jki | 2 | 13:28 |
| jki | 1 | 13:28 |
| jki | #topic AOB | 13:28 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:28 | |
| jki | FYI: my erofs problem was a kernel bug | 13:28 |
| pave1 | Good. so -- solved? | 13:29 |
| jki | arm32-only, patch is on the way, also for stable - kudos to the erofs maintainer | 13:29 |
| jki | https://lore.kernel.org/linux-erofs/da52a0d3-9a3b-4465-bf17-cf2ad8044330@linux.alibaba.com/T/#u | 13:30 |
| jki | anything else for today? | 13:30 |
| jki | 5 | 13:31 |
| jki | 4 | 13:31 |
| jki | 3 | 13:31 |
| jki | 2 | 13:31 |
| jki | 1 | 13:31 |
| jki | #endmeeting | 13:31 |
| collab-meetbot` | Meeting ended Thu Jul 10 13:31:38 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:31 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-10-13.02.html | 13:31 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-10-13.02.txt | 13:31 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-10-13.02.log.html | 13:31 |
| *** 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:31 | |
| jki | thanks! | 13:31 |
| uli_ | thanks | 13:31 |
| iwamatsu__ | Thank you | 13:31 |
| pave1 | Thank you! | 13:31 |
| masami | thank you | 13:31 |
| *** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:31 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 13:31 | |
| arisut | thx | 13:32 |
| *** jki <jki!~jki@195.145.170.148> has quit IRC (Quit: Leaving) | 13:35 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has joined #cip | 14:03 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-56-160.cust.vodafonedsl.it> has quit IRC (Ping timeout: 248 seconds) | 16:56 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Ping timeout: 252 seconds) | 17:41 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has joined #cip | 17:45 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!