| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:02 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:05 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Remote host closed the connection) | 07:27 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 07:33 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:49 | |
| *** uli <uli!~uli@2001:4091:a247:8107:ba60:c2ea:d4c8:c4fc> has joined #cip | 09:11 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 10:49 | |
| *** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip | 11:50 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:54 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:6b58:5f5b:5a6b:86b1> has joined #cip | 11:56 | |
| *** jki <jki!~jki@62.156.206.52> has joined #cip | 11:57 | |
| jki | hi all! | 12:00 |
|---|---|---|
| sietze | Hi! | 12:00 |
| uli | hello | 12:00 |
| masami | hello | 12:00 |
| fbezdeka | Hi! | 12:00 |
| patersonc[m] | Mornin | 12:00 |
| alicefm | morning | 12:00 |
| iwamatsu | hello | 12:01 |
| pave1 | hi! | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:02 |
| collab-meetbot | Meeting started Thu Jun 1 12:02:14 2023 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. create kernelci pipeline for buster images (arisut) | 12:02 |
| jki | any news on this? | 12:03 |
| alicefm | I gived a look today about how to integrate bullseye buster and bookworm used on kas/opt to the kernelci.yml file | 12:03 |
| alicefm | but still not sure how to proceed | 12:04 |
| alicefm | jki do you have any suggestion? | 12:05 |
| jki | are you unsure how to build what? | 12:06 |
| jki | already tried 'kas-container menu'? | 12:06 |
| alicefm | i see that kas added bullseye buster and bookworm container | 12:07 |
| alicefm | I'm trying to do same for the kernelci container | 12:07 |
| jki | we are currently building with bullseye containers, from buster to bookworm | 12:09 |
| jki | that is not an issue | 12:09 |
| alicefm | yes anyway will look into it and add it to the kernelci container | 12:10 |
| jki | ok - looks like kernelci.yml is not really stressed in CI or configurable via Kconfig | 12:10 |
| jki | hope it's not broken | 12:10 |
| jki | anyway, follow up with questions on the list if you have any | 12:11 |
| jki | other AIs? | 12:11 |
| alicefm | ok with others ai | 12:11 |
| alicefm | with going on | 12:11 |
| jki | #topic Kernel maintenance updates | 12:11 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:11 | |
| pave1 | I did reviews on 6.1.31 | 12:12 |
| masami | This week reported 5 new CVEs and 3 updated CVEs. | 12:12 |
| uli | i'm preparing 4.4 | 12:12 |
| iwamatsu | I reviewed 6.1.30 and 6.1.31 | 12:12 |
| pave1 | One thing from past -- Renesas wanted to merge counter driver and they needed to update counter subsystem to do that. | 12:12 |
| pave1 | (There were other options). | 12:13 |
| pave1 | I felt uneasy about that and they did not retry. | 12:13 |
| pave1 | If someone has opinions what to do there, we can discuss that. | 12:13 |
| jki | updating subsystems imply testing all other affected drivers, at least all in our configs... | 12:14 |
| jki | right? | 12:14 |
| pave1 | I am not sure we have counter subsystem enabled in our configs at all. | 12:15 |
| jki | maybe the counter subsystem would be on the edge by being comparably simple? | 12:17 |
| jki | didn't look at the patches, though, you likely did | 12:17 |
| iwamatsu | it is not enable. | 12:17 |
| pave1 | I am not sure there were patches :-). | 12:17 |
| pave1 | They asked if we wanted non-mainline driver or if we wanted to update the subsystem. | 12:17 |
| pave1 | I explained them we want neither :-). | 12:18 |
| jki | well, they need to propose at least some list of commits they would pick | 12:18 |
| pave1 | So the proposal is to update counter subsystem in 5.10-cip to 6.1 version (or so). | 12:19 |
| pave1 | Then merge the driver. | 12:19 |
| jki | if that update is reasonable, complete (all affected drivers), and reviewable | 12:20 |
| pave1 | Dunno. Well -- if another vendor needs other version of kernel then we are in trouble :-). | 12:21 |
| jki | then they also need to upgrade their driver to their mainline version ;) | 12:22 |
| patersonc[m] | Does CIP normally accept such subsystem "upgrades"? | 12:22 |
| jki | but, yes, it can become nasty | 12:22 |
| jki | if someone requested a DRM subsystem update, the answer would likely be simpler | 12:22 |
| jki | "no way" :) | 12:23 |
| pave1 | So... I don't believe it will cause problems in this concrete case. | 12:23 |
| pave1 | So... "We considered the proposal to update counter subsystem to XXX, and if we you are willing to do the work and submit reviewable patches, we will consider it" ? | 12:24 |
| jki | let them start with presenting a list / number of commits they would have to backport | 12:25 |
| jki | unless they have a backport to look at already | 12:25 |
| pave1 | Ok, I'll write something up. | 12:25 |
| patersonc[m] | Thanks | 12:27 |
| jki | perfect | 12:27 |
| jki | anything else on kernel maintenance? | 12:27 |
| jki | 4 | 12:28 |
| jki | 3 | 12:28 |
| jki | 2 | 12:28 |
| jki | 1 | 12:28 |
| jki | #topic Kernel release status | 12:28 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:28 | |
| jki | 4.4 | 12:28 |
| uli | sent the list of patches to review; most are trivial | 12:28 |
| uli | no problems expected | 12:29 |
| jki | good | 12:29 |
| jki | 4.19 | 12:29 |
| pave1 | will take a look, thatnks. | 12:29 |
| iwamatsu | on track | 12:29 |
| jki | any rt issues? | 12:30 |
| pave1 | Probably on Monday. | 12:30 |
| pave1 | -rt: I still have patches I'm porting. | 12:30 |
| jki | ok | 12:31 |
| jki | 5.10 | 12:31 |
| pave1 | (I meant 4.4-rt I still have a series and should do update soon. 4.19/5.10 should be on track). | 12:32 |
| jki | thanks for clarifying | 12:32 |
| jki | i suppose 5.10 is generally on track | 12:32 |
| jki | where are we with 6.1 by now? | 12:33 |
| pave1 | Busy with reviews in this part of cycle. | 12:33 |
| pave1 | Should continue when there is less to review :-). | 12:33 |
| pave1 | Next step is adding gitlab-ci.yml | 12:33 |
| jki | ok | 12:33 |
| jki | then let's move on | 12:34 |
| jki | #topic Kernel testing | 12:34 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:34 | |
| alicefm | 6.1 is on kernelci | 12:35 |
| jki | anything else on testing? | 12:37 |
| alicefm | im now working on getting isar cip core debian versions tested with respective kernel | 12:37 |
| alicefm | nothing else | 12:38 |
| jki | ok, then moving on in... | 12:38 |
| patersonc[m] | I don't think there's anything from me, just the usual maintenance etc. | 12:38 |
| jki | 5 | 12:38 |
| jki | 4 | 12:38 |
| jki | 3 | 12:38 |
| jki | 2 | 12:38 |
| jki | 1 | 12:38 |
| jki | #topic AOB | 12:38 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:38 | |
| patersonc[m] | o/ | 12:38 |
| patersonc[m] | EOSS is later this month. Do you think we can/should aim to have our first 6.1 release by then? | 12:38 |
| patersonc[m] | Then we'll have something to announce etc... | 12:39 |
| patersonc[m] | Unless we needed the E-TSC to go through anything | 12:39 |
| jki | would be nice - but makes my question above more concrete | 12:39 |
| jki | what is technically all missing? and until when could we finish this? | 12:40 |
| pave1 | We can probably do that. | 12:40 |
| jki | then I can ask for the OK from the TSC | 12:40 |
| jki | next TSC is next week | 12:40 |
| pave1 | Add yml, forward port 5.10 patches, then agree we are happy with the 6.1 version.. | 12:40 |
| iwamatsu | pavel, I can help them | 12:41 |
| jki | I can tell the TSC, "when we are done with X, Y, Z, we would release 6.1-cip - ok?" | 12:41 |
| jki | just tell me "X, Y, Z" :) | 12:42 |
| pave1 | Hmm. Let's just do X, Y, Z and tell them when its ready. | 12:43 |
| jki | next week might be the last chance before EOSS - I could image we will skip the one the week before | 12:43 |
| pave1 | Understood. | 12:43 |
| jki | if unlucky, we will only get the ok in the in-person meeting | 12:43 |
| jki | but that is Monday of the EOSS week | 12:43 |
| jki | might still be early enough... | 12:43 |
| jki | if we tag then quickly | 12:43 |
| jki | I can ask next week for opinions and announce that we would ask for permission at EOSS | 12:44 |
| jki | would that be fine? | 12:44 |
| patersonc[m] | Sure | 12:45 |
| iwamatsu | +1 | 12:45 |
| pave1 | Lets see. We might have "6.1-cip was released" for EOSS, or we could have "6.1-cip will be real soon now" :-). | 12:45 |
| patersonc[m] | pave1 let me know if there is anything you need me to help with | 12:45 |
| pave1 | patersonc, iwamatsu: yes, will do, thanks! | 12:46 |
| jki | perfect, that's a plan | 12:46 |
| jki | anything else? | 12:46 |
| jki | 5 | 12:47 |
| jki | 4 | 12:47 |
| jki | 3 | 12:47 |
| jki | 2 | 12:47 |
| jki | 1 | 12:47 |
| jki | #endmeeting | 12:47 |
| collab-meetbot | Meeting ended Thu Jun 1 12:47:37 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:47 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-01-12.02.html | 12:47 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-01-12.02.txt | 12:47 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-01-12.02.log.html | 12:47 |
| *** 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:47 | |
| jki | thanks, all! | 12:47 |
| pave1 | thank you! | 12:47 |
| uli | thank you | 12:47 |
| iwamatsu | thank you! | 12:47 |
| masami | thanks | 12:47 |
| alicefm | thanks. | 12:49 |
| patersonc[m] | Who is going to EOSS btw? | 12:49 |
| jki | o/ | 12:49 |
| uli | o/ | 12:49 |
| iwamatsu | o/ | 12:50 |
| pave1 | I should probably get the registration. | 12:50 |
| iwamatsu | if I get a ticket | 12:50 |
| patersonc[m] | Same! | 12:52 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:54 | |
| *** uli <uli!~uli@2001:4091:a247:8107:ba60:c2ea:d4c8:c4fc> has left #cip (Leaving) | 13:00 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 13:01 | |
| *** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving) | 13:36 | |
| *** jki <jki!~jki@62.156.206.52> has quit IRC (Quit: Leaving) | 13:57 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 15:32 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:6b58:5f5b:5a6b:86b1> has left #cip | 15:43 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 16:30 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 17:03 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 246 seconds) | 21:45 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!