*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:48 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 06:53 | |
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip | 07:36 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 11:50 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 12:27 | |
*** masami <masami!~masami@FL1-122-135-239-77.tky.mesh.ad.jp> has joined #cip | 12:57 | |
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:3eb3:1dcc:4cfa:5384> has joined #cip | 13:00 | |
pave1 | Hi! | 13:00 |
---|---|---|
masami | hello | 13:01 |
iwamatsu__ | hello | 13:01 |
patersonc | Howdy | 13:01 |
uli_ | hello | 13:01 |
pave1 | #startmeeting CIP IRC weekly meeting | 13:02 |
collab-meetbot | Meeting started Thu Mar 20 13:02:03 2025 UTC and is due to finish in 60 minutes. The chair is pave1. 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 | |
pave1 | #topic AI review | 13:02 |
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
pave1 | - share release scripts/procedures [pavel, iwamatsu-san] | 13:02 |
pave1 | I guess we should have jki for this one? | 13:02 |
pave1 | 3 | 13:02 |
pave1 | 2 | 13:02 |
pave1 | 1 | 13:02 |
pave1 | #topic Kernel maintenance updates | 13:02 |
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
iwamatsu__ | I am going to send it after this meeting. | 13:03 |
pave1 | I was reviewing 6.1.131 & .129. | 13:03 |
masami | This week reported 2 new CVEs and 110 updated CVEs. | 13:03 |
pave1 | Aha, ok, thank you! | 13:03 |
iwamatsu__ | I reviewed v6.1.130. | 13:03 |
uli_ | released 4.4 and 4.19 | 13:03 |
masami | I updated cip-kernel-sec yaml format to add version information. | 13:03 |
pave1 | Plus, 6.12-cip is now started. | 13:03 |
iwamatsu__ | masami, pave1: thank you! | 13:04 |
pave1 | Thank you, anything else? | 13:04 |
pave1 | 3 | 13:04 |
pave1 | 2 | 13:05 |
pave1 | 1 | 13:05 |
pave1 | #topic Kernel release status | 13:05 |
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
pave1 | linux-6.1.y-cip: interval 15 day | 13:05 |
pave1 | latest version release date: Wed Mar 5 05:05:09 AM UTC 2025 | 13:05 |
pave1 | limit date: Thu Mar 20 05:05:09 AM UTC 2025 | 13:05 |
pave1 | Status: *Late* | 13:05 |
pave1 | linux-6.1.y-cip-rt: interval 30 day | 13:05 |
pave1 | latest version release date: Fri Feb 14 05:24:30 PM UTC 2025 | 13:05 |
pave1 | limit date: Sun Mar 16 05:24:30 PM UTC 2025 | 13:05 |
pave1 | Status: *Late* | 13:05 |
pave1 | -cip-rt: I need upstream -rt release for that. I'll ask if it does not appear soon. | 13:05 |
iwamatsu__ | I am working for 6.1.y-cip | 13:06 |
pave1 | Thank you! | 13:06 |
pave1 | 3 | 13:06 |
pave1 | 2 | 13:07 |
pave1 | 1 | 13:07 |
pave1 | #topic Kernel testing | 13:07 |
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
arisut | working on adding CIP configs to KernelCI | 13:07 |
patersonc | Not much from me. I'm just looking into seeing if we can do without the gitlab-ci file for linux-cip | 13:07 |
pave1 | Yep, thank you. | 13:07 |
patersonc | I'd be able to add some default behaviour based on branch name, e.g. run pipeline x if branch y | 13:08 |
pave1 | 6.12-cip is in the git, testing it one way or another would be good. | 13:08 |
patersonc | For custom dev branches you may be better to add your own .gitlab-ci still, or you'd have to have known branches per kernel version | 13:08 |
pave1 | Basing it on branch name would work for 6.12.cip. | 13:09 |
pave1 | Can we do that? | 13:09 |
pave1 | iwamatsu: do we have good enough configs to start testing? | 13:09 |
iwamatsu__ | pave1: yes. we have enough configs. | 13:09 |
patersonc | They'd need to be copied into a 6.12.y-cip though. And -rt ones added | 13:10 |
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 13:10 | |
pave1 | patersonc: Could we get some kind of regexp? Automatically testing test-4.19 as ... 4.19 would make sense, and I could just push into appropriate ci/pavel/test-6.1 or so branch for testing. | 13:11 |
patersonc | pave1: That's what I'm just looking into | 13:11 |
pave1 | patersonc: THank you! | 13:11 |
pave1 | patersonc: We probably won't have separate branches for -rt in 6.12. | 13:11 |
pave1 | patersonc: But its true that separate configs for rt and non-rt configs would still make sense. | 13:12 |
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip | 13:12 | |
pave1 | But even non-rt testing would be useful at this point. I cherry-picked 20 or so renesas patches, verifying it still builds and boots would be good. | 13:13 |
patersonc | With the current way the build scripts work it would actually be better to merge the -rt configs into the non-rt dir if we're not having a separate branch | 13:13 |
pave1 | Ok, maybe you can coordinate with iwamatsu-san on the mailing list? I guess we'll need more | 13:18 |
patersonc | Sure | 13:18 |
pave1 | input about the rt configurations, for which boards, etc. But we should be able to get basic | 13:19 |
iwamatsu__ | Sure. | 13:19 |
pave1 | testing going with what we have. | 13:19 |
pave1 | Thanks! | 13:19 |
pave1 | 3 | 13:19 |
pave1 | 2 | 13:19 |
pave1 | 1 | 13:19 |
pave1 | #topic AOB | 13:19 |
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:19 | |
pave1 | Anything else? | 13:19 |
pave1 | 5 | 13:19 |
iwamatsu__ | I can not attend next meeting. | 13:19 |
pave1 | Ok, thanks for information. | 13:20 |
pave1 | 5 | 13:20 |
pave1 | 4 | 13:20 |
pave1 | 3 | 13:20 |
pave1 | 2 | 13:20 |
pave1 | 1 | 13:20 |
pave1 | #endmeeting | 13:20 |
collab-meetbot | Meeting ended Thu Mar 20 13:20:43 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:20 |
collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-20-13.02.html | 13:20 |
collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-20-13.02.txt | 13:20 |
collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-20-13.02.log.html | 13:20 |
*** 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:20 | |
pave1 | Thank you all! | 13:20 |
uli_ | thanks | 13:20 |
iwamatsu__ | Thank you! | 13:20 |
masami | thank you | 13:20 |
arisut | thx | 13:21 |
patersonc | iwamatsu__ do you need me to create an MR to copy the 6.12 configs or will you do it? | 13:21 |
*** masami <masami!~masami@FL1-122-135-239-77.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:22 | |
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Quit: Konversation terminated!) | 14:32 | |
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip | 14:40 | |
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:3eb3:1dcc:4cfa:5384> has quit IRC (Quit: Client closed) | 15:22 | |
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has quit IRC (Ping timeout: 260 seconds) | 17:43 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!