13:02:49 <jki> #startmeeting CIP IRC weekly meeting
13:02:49 <collab-meetbot`> Meeting started Thu Feb 16 13:02:49 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:49 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:49 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:56 <jki> #topic AI review
13:03:01 <jki> 1. enable more stable trees for testing (patersonc)
13:03:08 <pave1> Hello...
13:03:50 <patersonc[m]> No updates yet
13:04:04 <jki> any help needed?
13:04:44 <patersonc[m]> Just time, sorry
13:04:57 <jki> np
13:05:04 <jki> 2. report 6.1 test plan to LKML (pavel)
13:05:12 <patersonc[m]> There's nothing that hard to do, unless the kernel doesn't want to run on our boards
13:05:22 <pave1> Waiting for (1).
13:05:35 <jki> yeah, just to track both
13:05:41 <jki> other AIs?
13:06:08 <jki> 3
13:06:10 <jki> 2
13:06:11 <jki> 1
13:06:14 <jki> #topic Kernel maintenance updates
13:06:51 <masami> This week reported 2 new CVEs and no updated CVEs.
13:07:00 <uli> was out most of the week, no updates. still reviewing 5.10.168.
13:07:01 <pave1> I'm currently travelling, but did few reviews on 5.10.X.
13:07:20 <iwamatsu`> I reviewd 5.10.168
13:09:32 <jki> anything else here?
13:10:25 <jki> 3
13:10:27 <jki> 2
13:10:29 <jki> 1
13:10:32 <jki> #topic Kernel release status
13:10:39 <jki> - 4.4
13:10:50 <uli> on track. 4.14 patches are a bit less likely to apply cleanly than 4.9 did.
13:11:05 <uli> but that's expected, i guess
13:11:05 <pave1> IIRC -rt in 4.4 and 4.19 should be on track
13:11:23 <jki> - 4.19 (partly already answered)
13:12:09 <iwamatsu`> no issue. on track.
13:12:13 <jki> - 5.10
13:12:28 <iwamatsu`> same 4.19.
13:12:37 <jki> great
13:12:40 <jki> #topic Kernel testing
13:12:48 <pave1> uli -- I believe -stable approach is 'if it does not apply we drop it... So you simply did not  see the problematic patches.
13:12:54 <pave1> 5.10-rt
13:13:18 <pave1> I believe that one should be done when we have version match.
13:13:27 <alicef> updated the Use cip-kernel-configs for kernels (5.10.y-cip, 4.4.y-cip) PR to kernelci-core
13:13:56 <patersonc[m]> Thank you alicef
13:14:06 <alicef> removed rpc_defconfig on all the version as is just giving errors
13:14:38 <alicef> but noticed now that I maybe missed the kselftest fragments that I will add in the next days
13:15:33 <alicef> currently testing it with kernelci staging
13:17:06 <alicef> https://github.com/kernelci/kernelci-core/pull/1705
13:18:00 <jki> great
13:18:08 <alicef> I'm currently considering what other defconfig we don't need
13:19:09 <alicef> oh and also added risv configuration for 5.10.y-cip
13:19:41 <alicef> using cip-kernel-config
13:20:16 <jki> which is THE defconfig
13:21:14 <jki> fbezdeka: you are trying to follow up with Daniel regarding stable RT, kernel-ci & Co.
13:21:32 <fbezdeka> Right. But no response so far...
13:21:45 <jki> too fresh, let's see
13:23:42 <jki> anything else?
13:24:43 <patersonc[m]> Not from me
13:25:00 <jki> 3
13:25:02 <jki> 2
13:25:04 <jki> 1
13:25:06 <jki> #topic AOB
13:26:10 <pave1> There may be another CPU bug being worked around by mainline.
13:26:21 <jki> Intel again?
13:26:38 <alicef> mmm looks like riscv cip-kernel-config work but is not catching any riscv test. problably still need to implemented. https://staging.kernelci.org/build/id/63ee16e8dbf35ba5f59d58c6/
13:27:18 <pave1> intel probably. will need to investigate.
13:27:36 <jki> no risc-v at all in kernel-ci so far??
13:28:12 <jki> pavel: where did you pick this info up from? strange commits or direct channels?
13:28:15 <alicef> there is already riscv, just is missing some specific tests framgments
13:29:19 <pave1> jki -- diffstat, so far.
13:31:01 <jki> well, then let's watch the news
13:31:05 <jki> anything else?
13:31:45 <alicef> I probably need to look into risc-v fragments, will look into it in the next days
13:32:10 <jki> alicef: TIA!
13:33:07 <jki> then, closing in...
13:33:09 <jki> 3
13:33:12 <jki> 2
13:33:14 <jki> 1
13:33:16 <jki> #endmeeting