12:03:19 <jki_> #startmeeting CIP IRC weekly meeting
12:03:19 <collab-meetbot> Meeting started Thu May 11 12:03:19 2023 UTC and is due to finish in 60 minutes.  The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:03:19 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:03:19 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:03:26 <jki_> #topic AI review
12:03:30 <jki_> 1. create kernelci pipeline for buster images (arisut)
12:03:51 <arisut> sorry I was busy this week going on next week on this
12:04:03 <jki_> ok
12:04:13 <jki_> anything else regarding AIs?
12:04:29 <jki_> 3
12:04:31 <jki_> 2
12:04:33 <jki_> 1
12:04:35 <jki_> #topic Kernel maintenance updates
12:04:44 <uli> i'm reviewing 6.1.28
12:04:55 <masami> This week reported 9 new CVEs and 3 updated CVEs.
12:04:58 <pave1> I'm revewing 6.1.28. It is a huge one.
12:05:24 <iwamatsu> I did not work this week, sorry.
12:06:27 <jki_> anything else?
12:06:53 <jki_> 3
12:06:54 <jki_> 2
12:06:56 <jki_> 1
12:06:59 <jki_> #topic Kernel release status
12:07:04 <jki_> -4.4
12:07:08 <uli> on track
12:07:24 <jki_> -4.19
12:07:25 <pave1> 4.4-rt should be on track, too.
12:07:35 <jki_> yep
12:07:43 <iwamatsu> No new releases for LTS and RT...
12:08:08 <jki_> did anyone reach out to RT already?
12:08:21 <jki_> or was that for 5.10?
12:08:33 <pave1> That was for 5.10.
12:08:48 <jki_> right, we are still on track here
12:08:50 <jki_> good
12:08:55 <jki_> -5.10
12:08:58 <pave1> As far as I can tell, 4.19-rt and 5.10-rt would be both useful for us.
12:09:24 <pave1> At May 5th, 5.10.179-rt87  appeared in v5.10-rt-next.
12:09:37 <pave1> If real release does not appear soon, I'll do the asking.
12:09:51 <jki_> fine
12:09:53 <pave1> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v5.10-rt-next
12:11:01 <jki_> good
12:11:10 <jki_> #topic Kernel testing
12:11:24 <patersonc[m]> Hello
12:11:58 <patersonc[m]> I have a question for kernel people - at the moment we aren't testing the CIP kernel trees with x86/arm/arm64 defconfigs. Should we be?
12:12:31 <pave1> Good question.
12:12:36 <pave1> Compile testing really would not hurt.
12:12:59 <pave1> For x86 it should be testable on our targets.
12:13:21 <pave1> For arm/arm64, I'm not that sure, but if it boots & works, we should make sure it keeps booting/working.
12:13:27 <patersonc[m]> arm/arm64 defconfigs should run on the renesas boards AFAIK
12:14:02 <jki_> I suspect the defconfigs also run in qemu
12:14:27 <patersonc[m]> Is that all a "yes" then?
12:14:42 <pave1> "Yes". :-)
12:14:46 <jki_> +1
12:14:49 <patersonc[m]> Thanks
12:15:05 <patersonc[m]> I'm not sure I have anything else this week
12:15:23 <jki_> someone had a question for you last week...
12:15:48 <jki_> pavel: "I may want to talk about 6.1 testing"
12:16:09 <arisut> I would like to remember that KernelCI is already testing CIP kernels with arm and arm64
12:16:25 <pave1> Yep. I guess we should either include gitlab.yml config in linux-6.1.x-cip tree.
12:16:50 <pave1> Or maybe we want to use same system we use to test -stable kernels where .yml is not required.
12:16:56 <pave1> Anyway we should start testing it.
12:16:59 <arisut> and also RISCV
12:17:01 <patersonc[m]> arisut: good point
12:17:26 <arisut> https://github.com/kernelci/kernelci-core/blob/main/config/core/build-configs-cip.yaml#L206
12:17:34 <patersonc[m]> pave1: i suggest you add the usual .gitlab-ci file to match up with the other CIP kernels
12:18:05 <pave1> I'd eventually like to switch away from that, but it will do for now.
12:18:32 <pave1> Can I copy the config from 5.10, or do I get version from you?
12:19:09 <patersonc[m]> You can copy. Just change 5.10 -> 6.1 and it should work
12:19:18 <pave1> Ok :-).
12:22:00 <jki_> anything else on testing?
12:22:23 <arisut> 6.1 will soon be added to kernelci testing
12:23:24 <jki_> 5
12:23:26 <jki_> 3
12:23:29 <jki_> 2
12:23:30 <jki_> 1
12:23:35 <jki_> 4 :)
12:23:37 <jki_> #topic AOB
12:24:07 <jki_> just a minor thing: next week is public holiday here, maybe elsewhere as well?
12:24:32 <pave1> We had the public holiday on May 8th.
12:24:59 <pave1> And May 1th. So no more of those for few months.
12:25:11 <jki_> I may be able to participate, but I may also oversleep it if unlucky
12:25:30 <jki_> would someone else take over the organization, just in case?
12:26:02 <iwamatsu> I can take over.
12:26:13 <pave1> Thank you :-).
12:26:14 <jki_> thanks a lot!
12:26:31 <jki_> anything else on AOBs?
12:26:36 <pave1> Y.
12:26:54 <patersonc[m]> ll
12:27:08 <pave1> On Tuesday's meeting there was question if we use linux-stable gitlab mirror.
12:27:37 <jki_> ah, right
12:27:45 <pave1> I don't, but it should be asked here.
12:28:14 <patersonc[m]> Do you mean https://gitlab.com/cip-project/cip-testing/linux-stable-rc/?
12:29:39 <pave1> jki knows more. Yes, I believe it is that one. It is 10GB or so, and gitlab has size limits, so TSC wanted to know how important it is for us really, IIUC.
12:30:18 <jki_> it was shrunk already IIUC, but that question remains valid
12:30:22 <patersonc[m]> I added that repo recently because the kernel.org version was having connectivity issues. We use it in our stable-rc CI
12:30:29 <patersonc[m]> I've now shrunk the repo to about 4Gb
12:30:38 <patersonc[m]> s/4Gb/4GB/
12:30:46 <patersonc[m]> So it's not an issue anymore
12:32:37 <jki_> ok - then let us revisit this when the repo hits 10G again ;)
12:32:41 <jki_> anything else?
12:32:51 <patersonc[m]> yep
12:32:58 <patersonc[m]> Did anyone see toscalix's question? https://ircbot.wl.linuxfoundation.org/logs/%23cip/%23cip.2023-05-09.log.html#t2023-05-09T08:16:33
12:33:23 <jki_> not yet
12:33:49 <jki_> well, we should likely ask for ownership transfer
12:33:58 <jki_> not sure, thought, who all should be owner
12:34:18 <jki_> +that functional account of the LF
12:34:25 <pave1> LF admins want access to everything, so they can take this one, too? :-)
12:34:51 <pave1> Or maybe it should be just deleted if we don't need it. But LF can do that too...
12:34:59 <jki_> next question would be what to do with it then
12:35:11 <jki_> we should at least keep the namespace reserved
12:35:28 <pave1> Agreed.
12:35:48 <jki_> yoshi and wolfgang are also members - whatever that means for them
12:38:37 <jki_> ok, who will handle that github case?
12:40:01 <jki_> if no one, I can write an email to him, yoshi and neal
12:41:25 <jki_> anything else?
12:42:04 <jki_> ...if I had Agustin latest email address
12:42:52 <pave1> github should have the address, no?
12:42:58 <jki_> toscalix[m]: please contact me and yoshi on that github namespace
12:43:11 <jki_> nope
12:44:38 <pave1> Feel free to contact him thorugh:
12:44:39 <pave1> Twitter: @toscalix
12:44:39 <pave1> Mail:
12:44:39 <pave1> Personal: toscalix(at)gmail(dot)com or abenito(at)kde(dot)org
12:44:39 <pave1> IRC nickname: toscalix in irc.libera.chat
12:44:56 <pave1> From https://toscalix.com/about/
12:45:14 <jki_> ah, missed that
12:45:16 <jki_> thanks
12:45:56 <jki_> ok, then let's close for today
12:46:07 <pave1> (Hmm. Not sure if I should be copying addresses into irc that is public & logged, but the address is publicly on web so hopefully that's ok).
12:46:17 <patersonc[m]> :)
12:46:23 <jki_> exactly :)
12:46:36 <jki_> 5
12:46:37 <jki_> 4
12:46:38 <jki_> 3
12:46:39 <jki_> 2
12:46:41 <jki_> 1
12:46:43 <jki_> #endmeeting