12:02:20 <jki> #startmeeting CIP IRC weekly meeting
12:02:20 <collab-meetbot`> Meeting started Thu Dec  8 12:02:20 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02:20 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:20 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:02:33 <jki> #topic AI review
12:02:36 <jki> 1. Add qemu-riscv to cip-kernel-config - patersonc
12:02:48 <jki> seems chris is not around
12:03:11 <jki> anything else? from last week?
12:03:51 <jki> 3
12:03:52 <jki> 2
12:03:54 <jki> 1
12:03:59 <jki> #topic Kernel maintenance updates
12:04:23 <pave1> I did some reviews on 5.10.157 and 158. We seem to reached the part of cycle when things are slowing down.
12:04:32 <uli> i reviewed all 4.4 patches that don't apply and updated v4.4.org
12:04:34 <masami> This week reported 9 new CVEs and 3 updated CVEs.
12:05:29 <iwamatsu`> I reviewed 5.10.157
12:05:47 <jki> "v4.4.org"?
12:06:02 <uli> that's a file we use to track patches for the 4.4 kernel
12:06:12 <jki> ah, ok
12:06:38 <pave1> It is in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git . That's how the tools work.
12:09:00 <jki> anything else?
12:09:34 <jki> 3
12:09:36 <jki> 2
12:09:38 <jki> 1
12:09:41 <jki> #topic Kernel release status
12:09:50 <jki> - 4.4
12:10:22 <pave1> We should be on track now.
12:10:32 <jki> yep
12:10:32 <pave1> Still: There's build problem iirc.
12:10:46 <pave1> And there are patches to be backported to 4.4-rt.
12:11:08 <jki> anything critical?
12:11:19 <pave1> We fixed the build problem but we did not do release.
12:11:42 <jki> how broad is the impact of the build issue?
12:11:53 <jki> single driver or whole subsystem?
12:12:04 <pave1> Looked more like single driver IIRC.
12:12:22 <jki> and the pending backports, anything critical?
12:12:42 <iwamatsu`> and current test pipeline has a issue, patersonc and I are fixing that.
12:12:59 <pave1> No, the -rt stuff should not be critical.
12:13:53 <jki> the next regular release for 4.4 falls into our vacation season here
12:14:48 <jki> just a note
12:14:51 <jki> anyway
12:15:09 <jki> - 4.19
12:15:58 <iwamatsu`> today new version has released, 4.19.268. I will work to release tomorrow.
12:16:23 <jki> and -rt is not yet due
12:16:41 <jki> - 5.10
12:17:03 <iwamatsu`> same as 4.19.
12:17:16 <jki> and 5.10-rt?
12:17:25 <iwamatsu`> -rt too.
12:17:42 <jki> so there is one coming soon as well?
12:18:23 <pave1> I guess we should do that when the next -rt release happens.
12:19:06 <jki> our schedule would be these, then let's hope lts-rt is coming soon
12:19:08 <jki> ok
12:19:20 <jki> #topic Kernel testing
12:19:55 <alicef> reviewing patersonc[m] PR
12:20:32 <alicef> about adding CIP 4.4-stable branches on kernelCI
12:20:39 <alicef> currently building it
12:22:07 <alicef> that's all for me
12:22:56 <jki> anyone anything else on this?
12:23:36 <jki> 3
12:23:38 <jki> 2
12:23:40 <jki> 1
12:23:43 <jki> #topic AOB
12:24:15 <jki> two topics from one side
12:24:18 <pave1> I don't think Renesas fix for the RISC-V problem is complete. But as Patersonc is not here, I'll probably need to sit down and write an email.
12:24:41 <jki> ah, that is interesting
12:24:49 <jki> wasn't able to look into it yet
12:25:08 <jki> will follow this curiously
12:25:39 <jki> my first topic: 6.1-cip
12:25:58 <jki> release and LTS announcement should be out next week
12:26:20 <jki> should I ask the TSC if we can start 6.1 development? are we ready?
12:26:32 <pave1> You don't want to do that :-).
12:26:45 <pave1> Ok, let me explain.
12:27:16 <pave1> For next cca 6 months, there'll be huge ammount of patches going to 6.1.X.
12:27:33 <pave1> If we create a branch now, we'll have a lot to review.
12:27:46 <pave1> With 5.10.X we started cca 6 months late.
12:28:07 <pave1> And we might want to do the same thing here.
12:28:51 <pave1> Otherwise yes, I guess it is just another branch, and we should get list of boards and prepare gitlab.yml files etc.
12:28:59 <jki> understood
12:29:19 <jki> how about announcing the intention and roadmap?
12:29:47 <pave1> Yes, we can do that.
12:30:27 <pave1> And I guess we should announce that patches for 5.10-cip should have corresponding 6.1-cip variant, too, and start collecting those.
12:30:38 <pave1> So there are some advantages to branching early, too.
12:31:11 <pave1> I guess we should also start to run our CI on all 6.1.X branches so we know what state that is in.
12:31:15 <jki> with "patches for 5.10-cip" you mean cip-specific feature backports, right?
12:31:49 <jki> then we setting up the infrastructure but not yet go into reviewing or merging procedures?
12:32:16 <pave1> Yes. We have rule that they need to be in mainline, but soon mainline will be 6.2-rc.
12:32:42 <iwamatsu`> And we also need to check the work of Debian. but they will probably use 6.1 because they match LTS.
12:33:07 <pave1> Its reviewing I'm worried about.
12:33:29 <pave1> iwamatsu: Thanks. And ... that one is rather critical.
12:33:46 <pave1> If Debian selects 6.3, we probably want to do that, too.
12:34:04 <jki> Debian freeze is in early January, right?
12:34:10 <iwamatsu`> yes
12:34:34 <jki> then we could also delay the CIP decisions until then
12:34:35 <iwamatsu`> but it will work from toolchain.
12:35:05 <jki> you mean the kernel version freeze is later?
12:36:06 <iwamatsu`> Perhaps it will be decided at the same time as toolchain.
12:37:13 <jki> ok
12:37:33 <jki> I will tease the topic to the TSC but not yet ask for any decisions
12:38:48 <jki> my second topic is patchwork for cip
12:38:56 <jki> are we using that for the kernel patches?
12:39:20 <pave1> I don't think it is too useful, actually.
12:39:46 <jki> I wanted to start using it for isar-cip-core patches, that's why I came across this
12:40:03 <jki> does anyone know how I can gain access to it?
12:40:25 <iwamatsu`> I use it sometime. for getting patch set.
12:40:41 <jki> ok, so more as an archive, not to track status
12:41:52 <iwamatsu`> about gain access : I dont have information about that.
12:43:16 <pave1> I'm trying to remember how I got the access, but I don't really.
12:43:41 <pave1> You can create your account yourself on the website.
12:43:55 <pave1> Then I guess you can write to kernel.org admins that you are with CIP project.
12:44:26 <jki> likely that helpdesk@kernel.org - will try
12:44:43 <pave1> Yep. Or konstantin.
12:44:57 <pave1> But that's probably right address. Do you have @kernel.org account?
12:45:07 <jki> nope, no longer
12:45:13 <jki> precondition?
12:45:21 <pave1> Aha, so that may be the hard part :-).
12:45:36 <pave1> Talk to helpdesk, maybe it is not need a precondition.
12:45:47 <pave1> Normally a GPG key signed by two other people is needed for kernel.org.
12:46:11 <pave1> But if you had it before... You  may be  still considered trusted.
12:46:52 <jki> that was long before the hack and the big reset
12:47:04 <jki> https://patchwork.kernel.org/project/cip-dev/ - there are maintainers listed, just not me
12:47:19 <jki> not sure, though, if that is related
12:47:21 <jki> will ask
12:48:02 <pave1> Maybe Chris would know the details..
12:49:29 <jki> anything other business for today?
12:50:36 <jki> 3
12:50:38 <jki> 2
12:50:40 <jki> 1
12:50:42 <jki> #endmeeting