| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Ping timeout: 255 seconds) | 00:55 | |
| *** alicef_ <alicef_!~none@gentoo/developer/alicef> has joined #cip | 00:55 | |
| *** ChanServ sets mode: +o alicef_ | 00:55 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 02:17 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:49 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 09:24 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 11:46 | |
| *** uli <uli!~uli@2001:4091:a245:8159:9912:56c5:3722:89bb> has joined #cip | 11:46 | |
| *** sietze <sietze!~sietze_va@http-v.fe.bosch.de> has joined #cip | 12:00 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 12:14 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 12:51 | |
| *** jki <jki!~jki@87.130.32.178> has joined #cip | 13:00 | |
| jki | hi everyone! | 13:00 |
|---|---|---|
| masami | hi | 13:01 |
| uli | hello | 13:01 |
| sietze | Good day | 13:01 |
| patersonc[m] | Hello | 13:01 |
| iwamatsu | hi | 13:01 |
| alicefm | Hello | 13:01 |
| jki | let's get it going | 13:03 |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot` | Meeting started Thu Mar 9 13:03:06 2023 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:03 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:03 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:03 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | #topic AI review | 13:03 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | 1. enable more stable trees for testing (patersonc) | 13:03 |
| patersonc[m] | We're now testing all of the LTS releases | 13:03 |
| jki | iirc, there were bbb issues left, right? | 13:03 |
| patersonc[m] | Yea | 13:03 |
| patersonc[m] | I've disabled testing with our BBB config for now | 13:03 |
| jki | ok | 13:04 |
| patersonc[m] | It likely needs to be updated, but I'm not sure where the original came from | 13:04 |
| patersonc[m] | And I can't see an equivalent upstream/google | 13:04 |
| patersonc[m] | iwamatsu: You did the original commit - any ideas? | 13:04 |
| iwamatsu | Sorry, I dont understand about it. | 13:06 |
| patersonc[m] | https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/commit/e28e124c4b0bdbf9d9552a3ee77ba29b4247f86f | 13:06 |
| jki | how to reproduce the bbb issue? use that condig with 6.1-LTS and try to boot? | 13:07 |
| jki | if so, then isar-cip-core should be able to generate such a broken image as well | 13:07 |
| jki | I have board at home and could give it try tomorrow if that helps | 13:08 |
| patersonc[m] | This is the bbb config trying to boot with v6.1 on BBB: https://lava.ciplatform.org/scheduler/job/869559 | 13:09 |
| patersonc[m] | It also didn't work with v5.15 | 13:09 |
| patersonc[m] | I'll add more details to the MR when I make it | 13:09 |
| patersonc[m] | So people can review there | 13:09 |
| iwamatsu | I see, i dont remenber... | 13:09 |
| iwamatsu | But I will check it. | 13:09 |
| patersonc[m] | iwamatsu: No worries, it was a long time agi! | 13:09 |
| patersonc[m] | s/agi/ago/ | 13:10 |
| patersonc[m] | Anyway, once the MRs are done for the LTS testing, shall I expand it to all of the active stable trees? (not just LTS) | 13:10 |
| pave1 | i believe that makes sense. | 13:11 |
| patersonc[m] | Okay | 13:12 |
| jki | so, consider this AI done already, or keep it open until that is done as well? | 13:12 |
| patersonc[m] | I think we can close it. The immediate goal was to get 6.1 testing started | 13:13 |
| jki | perfect | 13:14 |
| jki | 2. report 6.1 test plan to LKML (pavel) | 13:14 |
| pave1 | I did. | 13:14 |
| jki | oh, great! | 13:14 |
| jki | any reactions? | 13:15 |
| pave1 | I was under impression that we'll test everything, and may have confused that. | 13:15 |
| pave1 | Nothing so far. | 13:15 |
| jki | anyway - thanks! | 13:15 |
| jki | 3. clarify usage of .sources files in cip-kernel-config (patersonc) | 13:15 |
| patersonc[m] | pave1: I think so - and we'll get there :) | 13:16 |
| patersonc[m] | jki: I haven't emailed the ML yet, so action still pending | 13:16 |
| jki | ok | 13:16 |
| jki | 4. reach out to Greg regarding LTS (jan) | 13:16 |
| jki | still open on my side | 13:16 |
| jki | will try to ping Ben first, later today or tomorrow | 13:17 |
| jki | any other AIs? | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic Kernel maintenance updates | 13:17 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| uli | now reviewing 5.10.173 | 13:18 |
| masami | This week reported 11 new CVEs and 4 updated CVEs. | 13:18 |
| pave1 | I did reviews on autosel and 5.10.173. | 13:18 |
| alicefm | Gregkh is here | 13:18 |
| iwamatsu | I am reviewing 5.10.173. | 13:19 |
| pave1 | S | 13:19 |
| alicef_ | gregkh: <- jki | 13:19 |
| pave1 | I will need to finish review of 4.4 patches. Sorry for the delay. | 13:21 |
| gregkh | alicef_: ? I've been here for a very long time... | 13:21 |
| alicef_ | gregkh: :) | 13:23 |
| *** alicef_ is now known as alicef | 13:23 | |
| uli | pave1: i would appreciate that, it's been a while | 13:23 |
| jki | gregkh: don't feel disturbed - we would eventually like to understand the needs to make longer LTS sustainable (again) and would reach out for that, likely via LKML | 13:24 |
| gregkh | jki: there are no "needs" to do so, sorry. As I wrote in the LF Board meeting slide deck last week, "The 6 year LTS experiment has failed" | 13:24 |
| gregkh | especially given all of the new laws coming into play in the US and EU, long-term kernels just are not going to work at all. | 13:25 |
| gregkh | sorry. | 13:25 |
| gregkh | I predict 3 year max over time, but for now we'll try 4 years to get over the transition period. | 13:25 |
| gregkh | ideally we can get back to 2 years, but that needs help from some SoC vendors, which are doing the work now, so we might get there. | 13:26 |
| gregkh | anyway, good luck! | 13:26 |
| jki | that interpretation of regulations is new to me at least | 13:26 |
| jki | also talking to colleagues exposed to strict regulations already today | 13:27 |
| pave1 | We'll promised to maintain the kernel for 10 years. If law prevents that, we'd like to know... | 13:27 |
| jki | yep | 13:27 |
| gregkh | define "promised", if it's a contract, that's on you, sorry. | 13:27 |
| gregkh | if not, well, you can always change it :) | 13:28 |
| pave1 | Looks like it is on LF... | 13:28 |
| gregkh | on the LF? Hah, no, your working group only, the LF doesn't promise anything with regards to kernel stuff, you all know that :) | 13:28 |
| patersonc[m] | Indeed | 13:28 |
| pave1 | Well, fortunately it is not on -me-... | 13:29 |
| gregkh | then figure out who it is on and work with them please. good luck! | 13:30 |
| jki | the only one under contract in his context are suppliers (like my employer) with their customers | 13:30 |
| gregkh | and as for regulations, there's nothing that says "you can not change this kernel version and it must stay the same" in any regulation that I know of. | 13:30 |
| patersonc[m] | CIP always planned to do 10 years support before LTS was extended to 6 years. So there's nothing new for CIP here - just that we don't get 4 extra years of free maintenance from Greg anymore :) | 13:31 |
| gregkh | jki: great, then that's between your employer and their customers, that's not anything with the LF. | 13:31 |
| gregkh | patersonc[m]: exactly. | 13:31 |
| pave1 | But better explanation would still be welcome, and probably get that explanation to people in charge of CIP project. | 13:31 |
| gregkh | pave1: point them at the LF board meeting slides from last week, it has the details if they are curious. | 13:32 |
| gregkh | pave1: and it says what to do if they have questions. | 13:32 |
| jki | gregkh: yes, we only try to support them as community as this is what we recieve funding for | 13:32 |
| gregkh | I'll probably flesh it all out in a blog post eventually to make it more widely visible. | 13:32 |
| jki | the more I'd like to understand statements like "not going to work at all" | 13:33 |
| jki | that would be great! | 13:33 |
| pave1 | If someone had url for slides or blog post explanation, that would be welcome. | 13:33 |
| gregkh | jki: see the new US and EU rules for the reasoning about "not going to work". they have the details and requirements. | 13:33 |
| patersonc[m] | pave1: We should be able to get a copy of the slides from Neal | 13:34 |
| alicef | patersonc[m]: can you share the slides also with me? | 13:34 |
| pave1 | petersonc. ok, that makes sense. | 13:34 |
| alicef | once you get it from Neal | 13:35 |
| patersonc[m] | alicef: Sure when we get them | 13:35 |
| alicef | thanks | 13:35 |
| pave1 | So I understand it is LF lawyers saying 10 years can't be done? | 13:35 |
| *** alicef is now known as arisut | 13:36 | |
| jki | gregkh: I've read first statements from community perspectives, but those were about way more fundamental issues | 13:36 |
| gregkh | pave1: nope, not the LF lawyers. me :) | 13:36 |
| gregkh | pave1: the lawyers have not weighed in on it yet, as no one has asked them to. | 13:37 |
| gregkh | sorry, irc does not lend itself to in depth discussions like this. | 13:39 |
| gregkh | anyway, good luck all! | 13:39 |
| pave1 | Ok. I gues this for CIP TSC level or above, not for me. Hopefully slides will clear my curiosity. | 13:39 |
| pave1 | Thanks! | 13:39 |
| patersonc[m] | :) | 13:39 |
| patersonc[m] | Thanks gregkh | 13:40 |
| jki | thanks! | 13:40 |
| jki | ok, let's continue with "business as usual" for now ;) | 13:40 |
| jki | anything else regarding maintenance topics? | 13:40 |
| jki | 3 | 13:41 |
| jki | 2 | 13:41 |
| jki | 1 | 13:41 |
| jki | #topic Kernel release status | 13:41 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:41 | |
| jki | - 4.4 | 13:41 |
| uli | still waiting for reviews | 13:41 |
| jki | pavel: ? | 13:41 |
| jki | or anyone? | 13:42 |
| pave1 | Should have them no later than tommorow. sorry for delay. | 13:42 |
| uli | ok then. | 13:42 |
| jki | good | 13:43 |
| jki | - 4.19 | 13:43 |
| iwamatsu | LTS 4.19 is 4.19.275, and 4.19 of RT kernel is v4.19.271-rt120. no RT tracking. | 13:43 |
| jki | so, we are on schedule still? | 13:45 |
| jki | a new RT should come these weeks from us | 13:47 |
| jki | -5.10 | 13:48 |
| iwamatsu | right, but we can not release -cip-rt this week | 13:48 |
| iwamatsu | LTS 5.10 is 5.10.172. 5.10 of RT kernel is v5.10.168-rt83. on schedule yet. | 13:49 |
| jki | good | 13:49 |
| jki | then let's move on | 13:49 |
| jki | #topic Kernel testing | 13:49 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:49 | |
| patersonc[m] | Main thing from me was expanding the stable testing | 13:50 |
| patersonc[m] | Perhaps the only thing... | 13:51 |
| jki | ok - anyone anything else on testing? | 13:52 |
| arisut | https://github.com/kernelci/kernelci-core/pull/1705 | 13:52 |
| jki | nice! | 13:52 |
| arisut | the pr for using cip-kernel-configs on cip kernels with kernelCI as been merged | 13:52 |
| arisut | now we have 5.10.y-cip 4.4.y-cip and 4.19.y-cip testing cip-kernel-config with some kselftest test also | 13:53 |
| jki | good | 13:54 |
| jki | move on? | 13:54 |
| arisut | ok | 13:54 |
| jki | 3 | 13:55 |
| jki | 2 | 13:55 |
| sietze | one thing thing from my side | 13:55 |
| jki | go ahead! | 13:55 |
| sietze | I requested a chat with Chris considering test reporting | 13:55 |
| sietze | patersonc will you be able to make that? | 13:55 |
| sietze | Is there anybody else interested in that topic here? | 13:56 |
| patersonc[m] | sietze: Yes, sorry for not getting back | 13:56 |
| jki | will you do that exchange directly, or in a recorded irc? | 13:57 |
| jki | would possibly point some colleague afterward to it | 13:57 |
| sietze | I arranged a teams meeting, (bosch hosted I guess). But can invite anybody who's interested | 13:58 |
| sietze | Anyway, most important thing is that Chris will be there | 13:59 |
| sietze | If not, than IMHO the meeting will not make much sense | 13:59 |
| jki | then just summarize next time ;) | 13:59 |
| jki | tia! | 13:59 |
| jki | anything else? | 14:00 |
| patersonc[m] | sietze: Perhaps forward the invite to the cip-members mainling list | 14:00 |
| sietze | Ok, good. THanks for accepting. Will forward to cip-members then | 14:00 |
| sietze | Need to step out now | 14:01 |
| sietze | Thanks! | 14:01 |
| *** sietze <sietze!~sietze_va@http-v.fe.bosch.de> has quit IRC (Quit: Leaving) | 14:01 | |
| jki | #topic AOB | 14:01 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 14:01 | |
| patersonc[m] | sietze: Thanks | 14:01 |
| jki | anything on other business today? | 14:01 |
| jki | 5 | 14:02 |
| jki | 4 | 14:02 |
| jki | 3 | 14:02 |
| jki | 2 | 14:02 |
| jki | 1 | 14:02 |
| jki | #endmeeting | 14:02 |
| collab-meetbot` | Meeting ended Thu Mar 9 14:02:59 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:02 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-09-13.03.html | 14:02 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-09-13.03.txt | 14:02 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-09-13.03.log.html | 14:02 |
| *** 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/" | 14:03 | |
| jki | thank you all? | 14:03 |
| jki | ! :) | 14:03 |
| arisut | thanks | 14:03 |
| pave1 | thank you! | 14:03 |
| masami | thank you | 14:03 |
| uli | thanks | 14:03 |
| patersonc[m] | :D | 14:03 |
| *** jki <jki!~jki@87.130.32.178> has quit IRC (Quit: Leaving) | 14:03 | |
| patersonc[m] | TTFN | 14:03 |
| iwamatsu | thank you | 14:03 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 14:04 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 14:05 | |
| *** uli <uli!~uli@2001:4091:a245:8159:9912:56c5:3722:89bb> has left #cip (Leaving) | 14:08 | |
| *** sietze <sietze!~sietze_va@http-v.fe.bosch.de> has joined #cip | 15:06 | |
| *** sietze <sietze!~sietze_va@http-v.fe.bosch.de> has quit IRC (Quit: Leaving) | 15:12 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 15:12 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 17:14 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 21:36 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 268 seconds) | 22:51 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!