| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 02:08 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Read error: Connection reset by peer) | 02:08 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:04 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has joined #cip | 07:47 | |
| *** toscalix_ is now known as toscalix | 09:57 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 10:25 | |
| *** uli <uli!~uli@55d44eec.access.ecotel.net> has joined #cip | 10:39 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:48 | |
| *** jki <jki!~jki@147.161.235.25> has joined #cip | 11:55 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 11:58 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 11:59 | |
| jki | hi all | 12:00 |
|---|---|---|
| iwamatsu | hi | 12:00 |
| uli | hello | 12:00 |
| masami | hi | 12:00 |
| patersonc[m] | Hello | 12:00 |
| fbezdeka | Hi | 12:00 |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
| collab-meetbot | Meeting started Thu Sep 22 12:01:14 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:01 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | #topic AI review | 12:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | 1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm | 12:01 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 12:02 | |
| alicef | hello | 12:02 |
| alicef | no updates here | 12:02 |
| jki | 2. Check cip devices on kernelci old pull request - patersonc | 12:02 |
| patersonc[m] | No updates alas | 12:03 |
| jki | anything else? | 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 | |
| alicef | I updated the pr for r8a7743-iwg20d-q7 | 12:03 |
| alicef | and waiting for denys to reviewing it | 12:04 |
| pave1 | I have done reviews on 5.10.144/145. Preparing to move 4.4.X forward. | 12:04 |
| uli | done with 5.10.142 | 12:04 |
| masami | This week reported 5 new CVEs and 4 updated CVEs. | 12:04 |
| patersonc[m] | alicef: thanks, I forgot about that... | 12:04 |
| alicef | my talk was about the cip devices kernelci old pr as I was still writing it | 12:05 |
| alicef | patersonc[m]: np | 12:05 |
| iwamatsu | I do not work for kernel work in this week yet, sorry. | 12:05 |
| jki | anything else to exchange? | 12:09 |
| jki | 3 | 12:09 |
| jki | 2 | 12:09 |
| jki | 1 | 12:09 |
| jki | #topic Kernel testing | 12:09 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:09 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 12:10 | |
| patersonc[m] | As alicef said, work has been continuing on the older devices to get them running in KernelCI properly | 12:11 |
| patersonc[m] | I finally did some documentation updates | 12:11 |
| patersonc[m] | Not much else from me. Anything from you Alice? | 12:11 |
| alicef | I reviewed and merged the documentation | 12:11 |
| alicef | ps cip instance documentation can be seen here https://static.staging.kernelci.org/docs/instances/cip/ | 12:13 |
| patersonc[m] | I guess that's about it | 12:14 |
| jki | ok, then move on in... | 12:14 |
| jki | 3 | 12:14 |
| jki | 2 | 12:14 |
| jki | 1 | 12:15 |
| jki | #topic AOB | 12:15 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:15 | |
| jki | I had two topics | 12:15 |
| jki | 1. task distribution around 4.4 maintenance | 12:15 |
| jki | pavel: are you around? | 12:15 |
| pave1 | Yes, I am. | 12:15 |
| jki | we do not track the review tasks for 4.4 like for the other kernels, do we? | 12:16 |
| pave1 | I kind of assume that if it is in 4.9, it must be okay. | 12:16 |
| jki | I mean we do not split the work and record who will do what | 12:17 |
| pave1 | Then I append list of changes to v4.4.org in lts-commit-list repository. | 12:17 |
| pave1 | Review whatever did not apply, and when I'm reasonably satisfied I move 4.4 forward. | 12:17 |
| jki | means at all goes over your desk only | 12:18 |
| pave1 | Well, I do publish the changes in v4.4.org :-). | 12:18 |
| jki | as we had some delays with 4.4 in past and more work is coming with some 6.1-cip, we should apply work-split wherever reasonable | 12:19 |
| jki | also because of reduced risk when someone may not be available for some weeks | 12:19 |
| pave1 | We were doing coarse grained splits over email ("please look at /dev/random changes in X.Y.Z") | 12:20 |
| pave1 | If someone wants to play with the scripts and does next release, that's okay with me, too. | 12:21 |
| pave1 | But two people "cooperating" on one release.. I believe it would be easier for single person to do the work. | 12:21 |
| jki | this has pros and cons | 12:22 |
| jki | the pro is clearly that this is more efficient | 12:22 |
| jki | the con is that it will mean larger latency if that person is not available | 12:22 |
| jki | and a hard transfer if that lasts longer | 12:22 |
| pave1 | I believe splitting work at "few releases" level makes sense. | 12:23 |
| jki | that sounds like a good idea to me | 12:24 |
| pave1 | Basically around 6.1-rc5, it will make sense to push 4.4.X forward. | 12:24 |
| pave1 | It should be small enough task for single person | 12:24 |
| pave1 | I wrote the scripts so I know how to operate them, but it is not rocket science and there are notes in v4.4.org. | 12:25 |
| pave1 | If someone wants to take the task, I can answer questions / help / etc. | 12:25 |
| pave1 | [I guess i would make sense for that person to create proper docs at that point.] | 12:25 |
| uli | i think rather than reverse-engineering your process, it'd be better if you wrote it down | 12:26 |
| pave1 | I guess we should cooperate to create something. | 12:27 |
| jki | uli: so you would feel like picking up 4.4 eventually? | 12:28 |
| uli | if i get the time to do it, i'd be okay with that | 12:29 |
| iwamatsu | o/ me too | 12:30 |
| jki | well, if we are heading for one maintainer per kernel model, we will still have less maintainers than kernels ;) | 12:31 |
| jki | and we will need again someone to look after 6.1-cip-rt :( | 12:32 |
| pave1 | So.. I'd say that maintaining 4.4.X has become quite different from the other branches. | 12:32 |
| pave1 | For example, I believe it would make sense for iwamatsu to release 6.1-cipX and for me to release 6.1-cipX-rtX. | 12:33 |
| jki | however we split, I would welcome a lot if that split could increase the number of active maintainers for CIP | 12:35 |
| pave1 | I'd consider less frequent releases for the older kernels, but agreed, more maintainers is nice, too :-). | 12:36 |
| iwamatsu | I think so :-) | 12:37 |
| jki | good :) | 12:38 |
| jki | that already covered by second AOB item | 12:38 |
| jki | what would be next steps now? | 12:39 |
| pave1 | Next steps for 6.1-ci? | 12:40 |
| pave1 | 6.1-cip? | 12:40 |
| jki | next steps for ramping up uli, making 4.4 workflow transferable | 12:41 |
| jki | maybe also preparing for the next cip kernel, but more regarding estimating additional efforts | 12:42 |
| pave1 | I believe nothing for now. I finish the release. | 12:43 |
| jki | let's assume uli would take over 4.4: would that give you two enough time to handle all other kernels? | 12:43 |
| pave1 | Then when uli wants to do the next one, I give him instructions. In a week or so, he'll have next 4.4.X release :-). | 12:43 |
| jki | or would you need a similar level of review contributions by him like now? | 12:44 |
| iwamatsu | nice > next 4.4.y release | 12:44 |
| pave1 | Reviews are majority of work. I'd say we should keep that split. | 12:45 |
| pave1 | Handling 4.4.X is not that much work. | 12:45 |
| jki | then uli needs an impression about what additional work is needed for 4.4 | 12:45 |
| jki | and we were not yet in real backport needs there, right? | 12:46 |
| pave1 | We don't do much backporting, no. Plus we don't really have renesas submitting backports for inclusion. | 12:47 |
| jki | na, 4.4 is no longer enabling backport target | 12:48 |
| jki | just like 4.19 stopped that | 12:48 |
| pave1 | I think we can start with some small 4.4.X releases "soon" so that Uli learns the scripts. | 12:48 |
| jki | cool | 12:48 |
| jki | anything else? about this or beyond? | 12:50 |
| jki | 3 | 12:52 |
| jki | 2 | 12:52 |
| jki | 1 | 12:52 |
| jki | #endmeeting | 12:52 |
| collab-meetbot | Meeting ended Thu Sep 22 12:52:19 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:52 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-22-12.01.html | 12:52 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-22-12.01.txt | 12:52 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/09/cip.2022-09-22-12.01.log.html | 12:52 |
| *** 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:52 | |
| jki | thank you all! | 12:52 |
| pave1 | Thank you! | 12:52 |
| uli | thanks | 12:52 |
| patersonc[m] | Hi jki : If you have a second - could I ask if you or your colleagues have time to review the RZ/G2M Jailhouse patches Prabhakar posted last month? | 12:52 |
| alicef | thanks you | 12:52 |
| patersonc[m] | Thanks all | 12:52 |
| masami | thank you | 12:52 |
| jki | patersonc[m]: sure | 12:53 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:53 | |
| iwamatsu | thank you | 12:53 |
| fbezdeka | Thanks, bye | 12:53 |
| patersonc[m] | jki: For reference: https://www.mail-archive.com/jailhouse-dev@googlegroups.com/msg10968.html | 12:53 |
| jki | the problem is my overload, not their patches | 12:53 |
| jki | I haven't found time to process the whole jailhouse backlog while more things keep piling up | 12:53 |
| patersonc[m] | Sure, I understand | 12:54 |
| patersonc[m] | jki: Let me know if you need any action from us | 12:55 |
| jki | I'm trying to find someone to support here, but that is currently equally tricky | 12:55 |
| jki | right now not, will let you know | 12:56 |
| patersonc[m] | 👍️ | 12:56 |
| *** uli <uli!~uli@55d44eec.access.ecotel.net> has left #cip (Leaving) | 12:57 | |
| *** jki <jki!~jki@147.161.235.25> has quit IRC (Quit: Leaving) | 13:06 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 13:27 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 14:16 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 14:16 | |
| *** toscalix <toscalix!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has quit IRC (Quit: Konversation terminated!) | 15:04 | |
| *** toscalix_ <toscalix_!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has joined #cip | 15:04 | |
| *** toscalix_ is now known as toscalix | 15:04 | |
| *** toscalix <toscalix!~agustinbe@239.red-79-144-155.dynamicip.rima-tde.net> has quit IRC (Quit: Konversation terminated!) | 15:56 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 16:44 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 18:03 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 18:25 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds) | 21:56 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 252 seconds) | 23:54 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!