| *** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has quit IRC | 01:07 | |
| *** rynofinn____ <rynofinn____!sid362734@id-362734.lymington.irccloud.com> has joined #cip | 01:21 | |
| *** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has joined #cip | 05:18 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:08 | |
| *** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has quit IRC | 10:09 | |
| *** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has joined #cip | 11:03 | |
| *** uli <uli!~uli@55d462ea.access.ecotel.net> has joined #cip | 11:43 | |
| *** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip | 12:07 | |
| *** ironfoot_ is now known as ironfoot | 12:10 | |
| *** josiah|2 <josiah|2!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip | 12:54 | |
| *** pave1 <pave1!~pavel@88.103.239.154> has joined #cip | 12:56 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has joined #cip | 12:57 | |
| *** jki <jki!~jki@165.225.27.60> has joined #cip | 13:00 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
|---|---|---|
| brlogger | Meeting started Thu Oct 21 13:01:18 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | Hi everyone! | 13:01 |
| jki | please let us know if you are around | 13:01 |
| patersonc[m] | Hello | 13:01 |
| iwamatsu | hi | 13:01 |
| josiah|2 | Hi | 13:01 |
| masami | hi | 13:01 |
| uli | hello | 13:01 |
| pave1 | hi | 13:02 |
| alicef | o/ | 13:02 |
| jki | great, let's get started | 13:02 |
| jki | #topic AI review | 13:03 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | 1. Combine root filesystem with kselftest binary - iwamatsu & alicef | 13:03 |
| alicef | I went on on the CIP core work | 13:03 |
| alicef | we merged the pull request for using gz compressed rootfs on KernelCI and started testing the isar-cip-core images. | 13:03 |
| alicef | isar-cip-core looks booting up from KernelCI but currently we cannot login as there is a root password | 13:04 |
| alicef | https://lava.ciplatform.org/scheduler/job/482078#L809 | 13:04 |
| alicef | Would be useful for KernelCI to have the isar-cip-core password removed as the other rootfs are doing. | 13:04 |
| alicef | jki: any opinion on this ? | 13:04 |
| jki | that should be doable, though I don't have a pattern at hand | 13:04 |
| alicef | is ok to remove the password from the isar-cip-core? | 13:05 |
| jki | we could do that at least for the testing images being built | 13:05 |
| alicef | ok nice. I will try to work on that | 13:05 |
| jki | the "how" is not at hand for me, but we will find a solution | 13:06 |
| alicef | I also updated the storage fileserver script for making a latest directory (even if probably will not used on KernelCI) | 13:06 |
| alicef | and updated the isar-cip-core images https://storage.staging.kernelci.org/images/rootfs/cip/ | 13:06 |
| jki | would be an Isar topic (if not documented there) -> isar-users ML | 13:06 |
| jki | alicef: great progress, thanks a lot! | 13:07 |
| alicef | lastly not related to cip core, I also started adding missing devices from https://lava.ciplatform.org/scheduler/device_types that are still not on KernelCI (currently testing it) | 13:08 |
| alicef | that's all from me | 13:09 |
| jki | 2. Look into S3 artifact upload issues - patersonc | 13:09 |
| patersonc[m] | No update | 13:09 |
| jki | ok - any new AIs? | 13:10 |
| jki | 3 | 13:10 |
| jki | 2 | 13:10 |
| jki | 1 | 13:10 |
| jki | #topic Kernel maintenance updates | 13:10 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| pave1 | I have reviewed patches for 5.10.74, still reviewing 5.10.75. | 13:11 |
| uli | pushed 5.10.70/71 reviews, now reviewing 5.10.75 | 13:11 |
| masami | I sent CVE entry report. There is 7 new CVEs are reported in this week. | 13:11 |
| iwamatsu | I reviewed 5.10.74. | 13:11 |
| masami | I'll send backport patch of CVE-2021-20321 for 4.4. | 13:11 |
| jki | regarding maintenance efforts: are we still on track with past estimations, roughly? | 13:14 |
| jki | there were some concerns in the board, though I communicated that esitmations cannot be "exact", specifically here | 13:14 |
| pave1 | I see maybe +10% effort compared to previous year. | 13:15 |
| pave1 | It may decrease as 5.10 is getting older (and less active). | 13:16 |
| jki | are there specific reasons for that, like +X% patch rate, release rate etc.? | 13:16 |
| jki | right, so that natural curve of stable kernels "calmind down" | 13:17 |
| pave1 | I expect increase when we enter self-maintainence mode for 4.4 | 13:17 |
| pave1 | Yes. And last year I was reviewing "calm" 4.19, and now I'm reviewing "hot" 5.10 (and 4.19 too). | 13:17 |
| jki | understood | 13:19 |
| patersonc[m] | o/ | 13:19 |
| patersonc[m] | When does CIP intend to start cip specific tags of v5.10? | 13:20 |
| patersonc[m] | When some non-LTS patches are added? | 13:20 |
| iwamatsu | maybe it will be decide next long TSC meeting. | 13:20 |
| patersonc[m] | okay | 13:21 |
| jki | yes, that would be good point to discuss | 13:21 |
| patersonc[m] | I guess part of it is whether the board thinks we can afford it | 13:22 |
| pave1 | I believe we are ready to do that. | 13:22 |
| jki | an important aspect is that we as WG group can make it clear that we can handle the additional effort with available resource | 13:22 |
| pave1 | We are doing reviews anyway, which are the expensive part. | 13:22 |
| jki | that is an important point | 13:22 |
| pave1 | I believe we even checked that all patches in 4.19 tree are in 5.10 tree, too. | 13:23 |
| jki | in addition, there was and likely still is the expectation of having 3 maintainers working on the kernels | 13:23 |
| jki | at least being ready to do so if needed (longer absence, additional unexpected work etc.) | 13:24 |
| patersonc[m] | Okay :) | 13:25 |
| pave1 | OTOH... I believe we have zero CIP specific changes in 5.10 tree, so ... there's no advantage of using -cip tree. | 13:25 |
| jki | that is my technical argument as well when people ask | 13:25 |
| jki | may change, though | 13:25 |
| jki | and then there is also the psychological aspect of not yet having tagged... | 13:26 |
| jki | stronger commitment | 13:26 |
| patersonc[m] | pave1: Although as you say, we did add the missing patches from v4.19? | 13:26 |
| jki | at we bit-identical with LTS or are we not? | 13:27 |
| pave1 | jki, patersonc: Not sure really. We may have backported patches from 5.11 to 4.19, and those would need to go to 5.10. | 13:27 |
| pave1 | so there probably is reason for 5.10-cip already. | 13:28 |
| jki | then we should stress that | 13:28 |
| patersonc[m] | I've got a feeling we already did that | 13:28 |
| jki | but also update linux-5.10.y-cip... | 13:28 |
| patersonc[m] | At least, we looked at the Renesas side of things for that | 13:29 |
| jki | it's 4 months old on git.kernel.org | 13:29 |
| pave1 | I checked, and 5.10-cip has cip specific changes, such as 98eb71578 dt-bindings: pci: rcar-pci-ep: Document missing interrupts property | 13:30 |
| pave1 | So yes, we should probably update and release that. | 13:30 |
| jki | I'll add that as new AI | 13:30 |
| jki | and also adding that try to CI, I suppose | 13:30 |
| iwamatsu | There was no story that 5.10-CIP was delayed four months ago.... | 13:30 |
| jki | s/try/tree | 13:31 |
| alicef | 5.10-cip is already on kernelci | 13:32 |
| jki | ah, perfect | 13:33 |
| iwamatsu | And merge testing with the latest 5.10 tree is always done. | 13:33 |
| jki | then it's just about official updating that branch | 13:33 |
| iwamatsu | https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commits/ci/iwamatsu/linux-5.10.y-cip-rc | 13:34 |
| alicef | https://linux.kernelci.org/job/cip/branch/linux-5.10.y-cip/ | 13:34 |
| jki | ok - anything else under this topic? | 13:36 |
| jki | 3 | 13:36 |
| jki | 2 | 13:36 |
| jki | 1 | 13:36 |
| jki | #topic Kernel testing | 13:37 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:37 | |
| jki | all covered before already? | 13:38 |
| patersonc[m] | Nothing from me, I'll had over to alicef :) | 13:38 |
| alicef | i already exhausted my topics on kernel testing | 13:38 |
| jki | then move on in | 13:38 |
| jki | 3 | 13:38 |
| jki | 2 | 13:39 |
| jki | 1 | 13:39 |
| jki | #topic AOB | 13:39 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:39 | |
| jki | uli: you are working in the group for a while now - do things work for you? any feedback/impressions? | 13:41 |
| uli | works well for me so far | 13:42 |
| uli | we are still looking for a better way to distribute the work, i guess | 13:42 |
| pave1 | Yes. I looked, and while etherpad does what we need, it is probably easier to just place it into git repository somewhere. | 13:43 |
| pave1 | Alternatively we could distribute work based on first letter of patch subject. | 13:44 |
| pave1 | We should probably create new repository for this, and agree that commit messages will not be used there. | 13:44 |
| jki | maybe better on "commit number % developers" ;) | 13:45 |
| pave1 | jki: No. | 13:45 |
| pave1 | jki: You want series of related patches to go to the same person. | 13:45 |
| jki | right | 13:45 |
| uli | git repo sounds good to me | 13:46 |
| iwamatsu | +1 | 13:46 |
| pave1 | And I guess we all agree on "no real commit messages there"? | 13:47 |
| pave1 | Can we create repo ourselves? | 13:47 |
| jki | formally, we need an approval for any new "project" under cip-project/ | 13:48 |
| iwamatsu | or we can use gitlab snippets | 13:48 |
| jki | we can start on the playground and migrate later | 13:48 |
| iwamatsu | https://gitlab.com/cip-project/cip-kernel/linux-cip/-/snippets | 13:49 |
| jki | or use snippets if they are fine | 13:49 |
| pave1 | I have no experience with snippets. | 13:50 |
| pave1 | I guess repository could go under cip-project/cip-kernel/, but we'd want new repo there. | 13:51 |
| uli | is it actually necessary to put it in any "official" place? it's just for internal coordination after all. | 13:51 |
| jki | iwamatsu: could you propose a workflow based on snippets? | 13:51 |
| jki | and if you want a git repo instead, again my proposal to create something in cip-playground first | 13:52 |
| jki | that is "non-official" | 13:52 |
| jki | https://gitlab.com/cip-playground | 13:52 |
| iwamatsu | jki: OK, I will investigate and propose. | 13:52 |
| alicef | thanks | 13:55 |
| jki | thanks! | 13:56 |
| jki | any other topics for today? | 13:56 |
| jki | 3 | 13:57 |
| jki | 2 | 13:57 |
| jki | 1 | 13:57 |
| jki | #endmeeting | 13:57 |
| brlogger | Meeting ended Thu Oct 21 13:57:35 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:57 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-21-13.01.html | 13:57 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-21-13.01.txt | 13:57 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2021/10/cip.2021-10-21-13.01.log.html | 13:57 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 13:57 | |
| pave1 | thank you! | 13:57 |
| jki | thank you all! | 13:57 |
| patersonc[m] | ttfn | 13:57 |
| jki | have a nice day/evening | 13:57 |
| iwamatsu | thank you! | 13:58 |
| masami | thank you | 13:58 |
| uli | thank you | 13:58 |
| alicef | thanks you | 13:58 |
| *** pave1 <pave1!~pavel@88.103.239.154> has quit IRC | 14:00 | |
| *** josiah|2 <josiah|2!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC | 14:01 | |
| *** jki <jki!~jki@165.225.27.60> has quit IRC | 14:04 | |
| *** uli <uli!~uli@55d462ea.access.ecotel.net> has left #cip | 14:13 | |
| *** jki <jki!~jki@195.145.170.147> has joined #cip | 14:16 | |
| *** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has quit IRC | 16:01 | |
| *** jki <jki!~jki@195.145.170.147> has quit IRC | 16:11 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has quit IRC | 17:07 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 21:52 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!