| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 260 seconds) | 02:18 | |
| alicef | patersonc[m]: reviewed your PR https://github.com/kernelci/kernelci-core/pull/1544 | 06:41 |
|---|---|---|
| alicef | please update it | 06:41 |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:53 | |
| patersonc[m] | Thanks alicef | 07:16 |
| patersonc[m] | Silly copy+paste mistake :P | 07:16 |
| alicefm | Can you add Reviewed-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com> | 07:35 |
| patersonc[m] | I'd love to | 07:35 |
| patersonc[m] | alicef: Done | 07:36 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:06 | |
| *** tobsch <tobsch!~quassel@2003:a:d7a:1f00:3e05:5b4d:2f24:eacd> has joined #cip | 08:11 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 09:51 | |
| *** uli <uli!~uli@175.176.15.164> has joined #cip | 10:25 | |
| *** jki <jki!~jki@88.215.103.113> has joined #cip | 11:54 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:55 | |
| jki | Hi all! | 12:00 |
| uli | hello | 12:00 |
| pave1 | Hi! | 12:00 |
| alicef | hello | 12:00 |
| iwamatsu` | hi | 12:00 |
| masami | hi | 12:00 |
| jki | let's go | 12:02 |
| jki | #startmeeting CIP IRC weekly meeting | 12:02 |
| collab-meetbot` | Meeting started Thu Dec 8 12:02:20 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:02 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:02 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:02 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:02 | |
| jki | #topic AI review | 12:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:02 | |
| jki | 1. Add qemu-riscv to cip-kernel-config - patersonc | 12:02 |
| jki | seems chris is not around | 12:02 |
| jki | anything else? from last week? | 12:03 |
| jki | 3 | 12:03 |
| jki | 2 | 12:03 |
| jki | 1 | 12:03 |
| jki | #topic Kernel maintenance updates | 12:03 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| pave1 | I did some reviews on 5.10.157 and 158. We seem to reached the part of cycle when things are slowing down. | 12:04 |
| uli | i reviewed all 4.4 patches that don't apply and updated v4.4.org | 12:04 |
| masami | This week reported 9 new CVEs and 3 updated CVEs. | 12:04 |
| iwamatsu` | I reviewed 5.10.157 | 12:05 |
| jki | "v4.4.org"? | 12:05 |
| uli | that's a file we use to track patches for the 4.4 kernel | 12:06 |
| jki | ah, ok | 12:06 |
| pave1 | It is in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git . That's how the tools work. | 12:06 |
| jki | anything else? | 12:09 |
| jki | 3 | 12:09 |
| jki | 2 | 12:09 |
| jki | 1 | 12:09 |
| jki | #topic Kernel release status | 12:09 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:09 | |
| jki | - 4.4 | 12:09 |
| pave1 | We should be on track now. | 12:10 |
| jki | yep | 12:10 |
| pave1 | Still: There's build problem iirc. | 12:10 |
| pave1 | And there are patches to be backported to 4.4-rt. | 12:10 |
| jki | anything critical? | 12:11 |
| pave1 | We fixed the build problem but we did not do release. | 12:11 |
| jki | how broad is the impact of the build issue? | 12:11 |
| jki | single driver or whole subsystem? | 12:11 |
| pave1 | Looked more like single driver IIRC. | 12:12 |
| jki | and the pending backports, anything critical? | 12:12 |
| iwamatsu` | and current test pipeline has a issue, patersonc and I are fixing that. | 12:12 |
| pave1 | No, the -rt stuff should not be critical. | 12:12 |
| jki | the next regular release for 4.4 falls into our vacation season here | 12:13 |
| jki | just a note | 12:14 |
| jki | anyway | 12:14 |
| jki | - 4.19 | 12:15 |
| iwamatsu` | today new version has released, 4.19.268. I will work to release tomorrow. | 12:15 |
| jki | and -rt is not yet due | 12:16 |
| jki | - 5.10 | 12:16 |
| iwamatsu` | same as 4.19. | 12:17 |
| jki | and 5.10-rt? | 12:17 |
| iwamatsu` | -rt too. | 12:17 |
| jki | so there is one coming soon as well? | 12:17 |
| pave1 | I guess we should do that when the next -rt release happens. | 12:18 |
| jki | our schedule would be these, then let's hope lts-rt is coming soon | 12:19 |
| jki | ok | 12:19 |
| jki | #topic Kernel testing | 12:19 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:19 | |
| alicef | reviewing patersonc[m] PR | 12:19 |
| alicef | about adding CIP 4.4-stable branches on kernelCI | 12:20 |
| alicef | currently building it | 12:20 |
| alicef | that's all for me | 12:22 |
| jki | anyone anything else on this? | 12:22 |
| jki | 3 | 12:23 |
| jki | 2 | 12:23 |
| jki | 1 | 12:23 |
| jki | #topic AOB | 12:23 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:23 | |
| jki | two topics from one side | 12:24 |
| pave1 | I don't think Renesas fix for the RISC-V problem is complete. But as Patersonc is not here, I'll probably need to sit down and write an email. | 12:24 |
| jki | ah, that is interesting | 12:24 |
| jki | wasn't able to look into it yet | 12:24 |
| jki | will follow this curiously | 12:25 |
| jki | my first topic: 6.1-cip | 12:25 |
| jki | release and LTS announcement should be out next week | 12:25 |
| jki | should I ask the TSC if we can start 6.1 development? are we ready? | 12:26 |
| pave1 | You don't want to do that :-). | 12:26 |
| pave1 | Ok, let me explain. | 12:26 |
| pave1 | For next cca 6 months, there'll be huge ammount of patches going to 6.1.X. | 12:27 |
| pave1 | If we create a branch now, we'll have a lot to review. | 12:27 |
| pave1 | With 5.10.X we started cca 6 months late. | 12:27 |
| pave1 | And we might want to do the same thing here. | 12:28 |
| pave1 | Otherwise yes, I guess it is just another branch, and we should get list of boards and prepare gitlab.yml files etc. | 12:28 |
| jki | understood | 12:28 |
| jki | how about announcing the intention and roadmap? | 12:29 |
| pave1 | Yes, we can do that. | 12:29 |
| pave1 | And I guess we should announce that patches for 5.10-cip should have corresponding 6.1-cip variant, too, and start collecting those. | 12:30 |
| pave1 | So there are some advantages to branching early, too. | 12:30 |
| pave1 | I guess we should also start to run our CI on all 6.1.X branches so we know what state that is in. | 12:31 |
| jki | with "patches for 5.10-cip" you mean cip-specific feature backports, right? | 12:31 |
| jki | then we setting up the infrastructure but not yet go into reviewing or merging procedures? | 12:31 |
| pave1 | Yes. We have rule that they need to be in mainline, but soon mainline will be 6.2-rc. | 12:32 |
| iwamatsu` | And we also need to check the work of Debian. but they will probably use 6.1 because they match LTS. | 12:32 |
| pave1 | Its reviewing I'm worried about. | 12:33 |
| pave1 | iwamatsu: Thanks. And ... that one is rather critical. | 12:33 |
| pave1 | If Debian selects 6.3, we probably want to do that, too. | 12:33 |
| jki | Debian freeze is in early January, right? | 12:34 |
| iwamatsu` | yes | 12:34 |
| jki | then we could also delay the CIP decisions until then | 12:34 |
| iwamatsu` | but it will work from toolchain. | 12:34 |
| jki | you mean the kernel version freeze is later? | 12:35 |
| iwamatsu` | Perhaps it will be decided at the same time as toolchain. | 12:36 |
| jki | ok | 12:37 |
| jki | I will tease the topic to the TSC but not yet ask for any decisions | 12:37 |
| jki | my second topic is patchwork for cip | 12:38 |
| jki | are we using that for the kernel patches? | 12:38 |
| pave1 | I don't think it is too useful, actually. | 12:39 |
| jki | I wanted to start using it for isar-cip-core patches, that's why I came across this | 12:39 |
| jki | does anyone know how I can gain access to it? | 12:40 |
| iwamatsu` | I use it sometime. for getting patch set. | 12:40 |
| jki | ok, so more as an archive, not to track status | 12:40 |
| iwamatsu` | about gain access : I dont have information about that. | 12:41 |
| pave1 | I'm trying to remember how I got the access, but I don't really. | 12:43 |
| pave1 | You can create your account yourself on the website. | 12:43 |
| pave1 | Then I guess you can write to kernel.org admins that you are with CIP project. | 12:43 |
| jki | likely that helpdesk@kernel.org - will try | 12:44 |
| pave1 | Yep. Or konstantin. | 12:44 |
| pave1 | But that's probably right address. Do you have @kernel.org account? | 12:44 |
| jki | nope, no longer | 12:45 |
| jki | precondition? | 12:45 |
| pave1 | Aha, so that may be the hard part :-). | 12:45 |
| pave1 | Talk to helpdesk, maybe it is not need a precondition. | 12:45 |
| pave1 | Normally a GPG key signed by two other people is needed for kernel.org. | 12:45 |
| pave1 | But if you had it before... You may be still considered trusted. | 12:46 |
| jki | that was long before the hack and the big reset | 12:46 |
| jki | https://patchwork.kernel.org/project/cip-dev/ - there are maintainers listed, just not me | 12:47 |
| jki | not sure, though, if that is related | 12:47 |
| jki | will ask | 12:47 |
| pave1 | Maybe Chris would know the details.. | 12:48 |
| jki | anything other business for today? | 12:49 |
| jki | 3 | 12:50 |
| jki | 2 | 12:50 |
| jki | 1 | 12:50 |
| jki | #endmeeting | 12:50 |
| collab-meetbot` | Meeting ended Thu Dec 8 12:50:42 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:50 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/12/cip.2022-12-08-12.02.html | 12:50 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/12/cip.2022-12-08-12.02.txt | 12:50 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/12/cip.2022-12-08-12.02.log.html | 12:50 |
| *** 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 12: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:50 | |
| jki | thank you all! | 12:50 |
| pave1 | Thank you! | 12:50 |
| uli | thanks | 12:50 |
| masami | thank you | 12:50 |
| iwamatsu` | thank you | 12:51 |
| *** uli <uli!~uli@175.176.15.164> has left #cip (Leaving) | 12:54 | |
| alicefm | thanks you | 12:55 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:55 | |
| *** jki <jki!~jki@88.215.103.113> has quit IRC (Quit: Leaving) | 12:57 | |
| alicef | pave1: are you still here ? | 14:37 |
| alicef | np I wanted to ask a question but I wait for patersonc[m] review answer | 14:40 |
| alicef | patersonc[m]: please check the review | 14:41 |
| pave1 | still here, but not sure how long this message was sitting here. | 15:19 |
| pave1 | Better do it over email, I guess? | 15:19 |
| pave1 | Sorry. | 15:19 |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 15:24 | |
| *** tobsch <tobsch!~quassel@2003:a:d7a:1f00:3e05:5b4d:2f24:eacd> has quit IRC (Ping timeout: 252 seconds) | 17:01 | |
| *** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:36c2:70ea:9c3c:6058> has joined #cip | 18:35 | |
| *** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:36c2:70ea:9c3c:6058> has quit IRC (Ping timeout: 265 seconds) | 19:25 | |
| *** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:596a:232f:d07f:a17d> has joined #cip | 21:24 | |
| *** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:596a:232f:d07f:a17d> has quit IRC (Ping timeout: 265 seconds) | 22:03 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 248 seconds) | 22:53 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!