| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Remote host closed the connection) | 04:57 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip | 04:58 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:50 | |
| *** hiromotai <hiromotai!~Hirotaka@219x123x27x194.ap219.ftth.ucom.ne.jp> has joined #cip | 11:00 | |
| *** hiromotai <hiromotai!~Hirotaka@219x123x27x194.ap219.ftth.ucom.ne.jp> has quit IRC (Quit: Leaving) | 11:53 | |
| *** jki <jki!~jki@62.156.206.31> has joined #cip | 12:58 | |
| jki | hi all | 13:00 |
|---|---|---|
| uli_ | hello | 13:00 |
| pave1 | hi! | 13:00 |
| arisut | hi | 13:01 |
| patersonc | hey | 13:01 |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 13:02 | |
| jki | ok, let'S go | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot` | Meeting started Thu Mar 6 13:02:51 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 | |
| jki | no open points | 13:03 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:03 |
| jki | 2 | 13:03 |
| jki | 1 | 13:03 |
| jki | #topic Kernel maintenance updates | 13:03 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| uli_ | i'm working on 4.19 and 4.4. | 13:03 |
| pave1 | I'm reviewing 6.1.129, 130 | 13:04 |
| jki | anything else? | 13:07 |
| jki | 5 | 13:08 |
| jki | 4 | 13:08 |
| jki | 3 | 13:08 |
| jki | 2 | 13:08 |
| jki | 1 | 13:08 |
| jki | #topic Kernel release status | 13:08 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:08 | |
| jki | all lights green again | 13:08 |
| jki | anything to add? | 13:08 |
| 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'm trying to use the gitlab configurations on kernelci | 13:09 |
| arisut | KernelCI team suggested to add configurations to the kernel repository | 13:10 |
| arisut | is that a possibility ? | 13:11 |
| jki | which configs? kernel configs? | 13:11 |
| arisut | cip-kernel-config | 13:11 |
| pave1 | Iwamatsu-san normally maintains that. | 13:12 |
| jki | right, and the sematic is important to CIP | 13:12 |
| jki | we can replicate them, but it may be tricky to maintain them in kernel ci | 13:12 |
| jki | and what is the "kernel repository" BTW? | 13:12 |
| jki | surely not upstream | 13:13 |
| arisut | that is one possibility | 13:13 |
| arisut | adding the configuration in the CIP kernel repository | 13:13 |
| jki | that makes no sense | 13:13 |
| jki | kernel configs are not maintained inside kernel trees anymore | 13:13 |
| pave1 | it is quite important to be able to test mainline trees. | 13:14 |
| jki | yes, but not via upstream's defconfigs | 13:14 |
| jki | that's why there are separate ones to enable more features when testing | 13:14 |
| arisut | testing mainline trees with the same CIP configurations? | 13:15 |
| pave1 | .gitlab.ci already breaks that, but adding also configs would be step in wrong direction. | 13:15 |
| patersonc | I guess the question is - what configs does CIP actually want/need to test? | 13:15 |
| jki | what we define in our config(s) | 13:15 |
| jki | yes, adding .gitlab.ci was an unnneed move for our kernel | 13:16 |
| jki | i'm sure we can eventually drop it again | 13:16 |
| patersonc | Well we can remove it soon when we move to KernelCI | 13:16 |
| jki | exactly | 13:16 |
| pave1 | arisut. yes, testing mainline or stable with our configs is valuable when bisecting. | 13:17 |
| arisut | pave1, I see | 13:17 |
| patersonc | I guess we'll have to find a way to use the out-of-tree configs arisut | 13:17 |
| jki | what does kernelci do otherwise? | 13:18 |
| jki | they surely don't ask Linus to add a .config for testing purposes | 13:18 |
| arisut | KernelCI use fragments of config saved in kernelCI configuration file | 13:19 |
| *** iwamatsu <iwamatsu!~iwamatsu@2405:6581:5360:1800:74f3:ad88:1be6:a7d1> has joined #cip | 13:19 | |
| jki | can we define our own fragments? | 13:21 |
| arisut | yes | 13:21 |
| jki | baseline is likely then the defconfig | 13:21 |
| iwamatsu | sorry, I'm late | 13:22 |
| arisut | That's true | 13:22 |
| jki | we would only have to generate a fragment that expresses the delta from there to cip config | 13:22 |
| arisut | right, that is probably the best way | 13:22 |
| arisut | I will look into it, thanks | 13:23 |
| jki | okay - then we have a plan for that :) | 13:23 |
| patersonc | Would the fragments need to be the same for each kernel version? | 13:23 |
| jki | thanks! | 13:23 |
| patersonc | I guess they could be | 13:23 |
| jki | probably not | 13:24 |
| pave1 | Patersonc. likely not. | 13:24 |
| arisut | patersonc, depend from the delta i suppose | 13:24 |
| jki | they will already be different per arch | 13:24 |
| arisut | of each version | 13:24 |
| arisut | yes | 13:24 |
| jki | goal for is still one merged config per arch and version | 13:24 |
| jki | btw: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/merge_requests/115 | 13:25 |
| jki | iwamatsu: please have a look | 13:25 |
| iwamatsu | Yes, I will check it. | 13:26 |
| jki | will solve the problem that some people only patched the merged configs now, breaking regeneration | 13:27 |
| jki | ok | 13:27 |
| jki | anything else on configs? | 13:27 |
| jki | or on testing? | 13:27 |
| jki | 5 | 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 | tomorrow is E-TSC - any inputs from that | 13:29 |
| jki | are we still on track with maintaining 4.4 + 4.19 ourselves? | 13:30 |
| uli_ | looks ok so far | 13:30 |
| arisut | release scripts as been added on gitlab? | 13:31 |
| jki | thanks for the reminder | 13:31 |
| jki | any news on that? | 13:31 |
| arisut | maybe this could be a AI | 13:32 |
| jki | yeah, just checking who to assign it to ;) | 13:32 |
| arisut | right | 13:32 |
| pave1 | I will send notes to the list, but they are meant for copy/pasting, not direct exec. | 13:33 |
| jki | iwamatsu... you wanted to share as well | 13:33 |
| jki | will add you both then | 13:33 |
| pave1 | and I suspect everyone has version modified for their environment, because they depend on it. | 13:34 |
| pave1 | plus uli likely has a copy as well .-) | 13:34 |
| uli_ | i copied my first announcement from iwamatsu-san, then i copied my own for every release | 13:34 |
| arisut | would be nice to add a config file and make it work on virtualenv | 13:35 |
| iwamatsu | I will share it. | 13:35 |
| jki | perfect | 13:35 |
| jki | anything to add for tomorrow regarding maintenance? | 13:35 |
| jki | if not: status 6.12, where are we? | 13:37 |
| patersonc | pave1 are you still planning to run your script that highlights what is missing from CIP commits in 6.12 compared to 6.1? | 13:37 |
| pave1 | Next steps are agreeing on configs, and porting changes from 6.1cip | 13:38 |
| iwamatsu | I send to ML about the config, but have not received a reply. | 13:38 |
| jki | then I can remind folks again | 13:39 |
| pave1 | PPP | 13:39 |
| pave1 | maybe we should agree on forking the tree from specific version tommorow. | 13:40 |
| jki | what should the TSC be asked then? | 13:40 |
| jki | we do have the ok already to start 6.12 development | 13:40 |
| jki | which naturally includes forking off | 13:41 |
| jki | plus there was the call for backports to 6.12 as well | 13:41 |
| jki | I suppose no one used that yet - or had to use it | 13:41 |
| pave1 | "We'll fork 6.12 from 6.12.123. Is everyone ok with that?" | 13:41 |
| pave1 | I guess. | 13:41 |
| pave1 | Or maybe we just need to agree between ourselves. | 13:42 |
| jki | were there any backports recently that were missing 6.12 support? | 13:42 |
| pave1 | there was such series this week,yes. | 13:43 |
| jki | iwamatsu: where is your call for configs again? | 13:43 |
| jki | pavel: did you give that feedback already? link? | 13:43 |
| pave1 | They said they are aware of the issue... | 13:44 |
| pave1 | and it is really not a problem, will handle it | 13:44 |
| pave1 | with the rest when running the script. | 13:45 |
| pave1 | Would have to search for the link. | 13:45 |
| jki | found the series | 13:45 |
| iwamatsu | jki: I will ping again to ML | 13:46 |
| pave1 | What about "pavel will write an email with version to fork from later today" | 13:46 |
| pave1 | and we'll get things moving on the tsc? | 13:47 |
| jki | well, we will try :) | 13:48 |
| pave1 | Ok .-) | 13:48 |
| jki | good | 13:48 |
| jki | then I had on my list: "feedback / next steps CVE triage tooling" | 13:49 |
| jki | my colleague is absent to refresh my memories, and masami is also not here today | 13:50 |
| jki | anthing to add, on that or other points for tomorrow? | 13:50 |
| jki | 5 | 13:53 |
| jki | 4 | 13:53 |
| jki | 3 | 13:53 |
| jki | 2 | 13:53 |
| jki | 1 | 13:53 |
| jki | #endmeeting | 13:53 |
| collab-meetbot` | Meeting ended Thu Mar 6 13:53:40 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:53 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-06-13.02.html | 13:53 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-06-13.02.txt | 13:53 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-06-13.02.log.html | 13:53 |
| *** 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:53 | |
| jki | thanks, see you tomorrow! | 13:53 |
| arisut | thx | 13:53 |
| uli_ | thanks | 13:53 |
| iwamatsu | Thank you | 13:54 |
| pave1 | thank you! | 13:57 |
| *** jki <jki!~jki@62.156.206.31> has quit IRC (Quit: Leaving) | 13:59 | |
| *** iwamatsu <iwamatsu!~iwamatsu@2405:6581:5360:1800:74f3:ad88:1be6:a7d1> has quit IRC (Quit: Leaving) | 13:59 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Ping timeout: 272 seconds) | 20:41 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip | 20:42 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!