12:01:16 <jki> #startmeeting CIP IRC weekly meeting
12:01:16 <collab-meetbot> Meeting started Thu May  5 12:01:16 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:16 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:16 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:17 <brlogger`> Meeting started Thu May  5 12:01:16 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:17 <brlogger`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:17 <brlogger`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:19 <jki> hi!
12:01:28 <uli> hello
12:01:41 <masami> hi
12:02:40 <pave1> Hi!
12:05:39 <jki> the round remains smaller today IIRC
12:05:46 <jki> so let's start
12:05:52 <jki> #topic AI review
12:06:02 <jki> 1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm
12:06:09 <jki> -skip-
12:06:18 <jki> 2. Document cip kernel release cadence in wiki - jki
12:06:51 <jki> didn't find what I was looking for yet, but I keep searching
12:07:28 <jki> #topic Kernel maintenance updates
12:07:47 <pave1> Reviewing 5.10.114 patches.
12:07:51 <uli> reviewing 5.10.114
12:07:52 <masami> There was 4 new CVEs and 2 updated CVEs this week. no notable issues.
12:08:41 <pave1> masami: Except another ugly BPF issue. BPF should be avoided for secure systems :-(.
12:09:40 <pave1> I beleive 4.4.y-cip-rebase patches are in wrong order. I sent an email with explanation.
12:09:51 <masami> pavel: yes, I think so too..
12:12:30 <jki> further topics here?
12:13:18 <jki> 3
12:13:19 <jki> 2
12:13:21 <jki> 1
12:13:24 <jki> #topic Kernel testing
12:13:29 <patersonc[m]> I'm here, sorry for being late
12:13:39 <jki> just in-time for this at least :)
12:13:43 <patersonc[m]> Although I don't have much to report on the testing front
12:13:53 <patersonc[m]> And no updates on the action
12:14:35 <jki> anyone else with testing topics?
12:15:15 <jki> was the socfpga thing resolved?
12:15:52 <patersonc[m]> Good question
12:16:08 <pave1> jki: yes. Greg reverted the patch, and -stable-rc testing now passes.
12:16:26 <jki> perfect
12:16:34 <pave1> jki: Further, there is a fix in -next or something.
12:17:00 <pave1> I believe we have not seen failures in our testing, so -cipXX should be fine.
12:17:48 <jki> okay
12:17:52 <jki> anything else?
12:18:20 <jki> 3
12:18:22 <jki> 2
12:18:23 <jki> 1
12:18:26 <jki> #topic AOB
12:19:58 <jki> patersonc[m]: are there already activities regarding riscv on your side?
12:21:05 <patersonc[m]> jki: yes
12:21:24 <patersonc[m]> Nothing much upstream yet, bit there is an alpha bsp
12:22:24 <jki> just wondering who may start on cip side with, e.g., setting up a qemu target
12:23:26 <jki> as long as it's getting more concrete in general, this step isn't urgent, though
12:23:41 <patersonc[m]> Hopefully it won't be too hard
12:24:11 <jki> we will know afterwards ;)
12:24:14 <pave1> I guess first step would be to set up testing of -stable 5.10.X or something like that...
12:25:10 <patersonc[m]> Yea
12:25:18 <jki> does kernelci consider riscv already?
12:25:44 <patersonc[m]> I'm not sure tbh
12:26:27 <jki> might be a lot of small & simple steps - but at least "a lot"
12:28:58 <jki> ok, anything else?
12:30:13 <jki> 3
12:30:15 <jki> 2
12:30:16 <jki> 1
12:30:18 <jki> #endmeeting