12:02:16 <jki> #startmeeting CIP IRC weekly meeting
12:02:16 <collab-meetbot> Meeting started Thu Jul 20 12:02:16 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02:16 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:16 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:02:21 <jki> #topic AI review
12:02:24 <jki> 1. create kernelci pipeline for buster images (arisut)
12:02:35 <pave1> Hello!
12:03:01 <arisut_> no news on this
12:03:20 <jki> ok
12:03:36 <jki> another AI I forgot:
12:03:49 <jki> 2. draft press release on 6.1 release (jan)
12:03:53 <jki> todo...
12:04:01 <jki> anything else?
12:04:17 <pave1> Nothing from last week, IIRC>
12:04:51 <jki> #topic Kernel maintenance updates
12:05:11 <pave1> Reviews on 6.1.39. This is huge one.
12:05:18 <uli> same here
12:05:19 <masami> This week reported 12 new CVEs and 4 updated CVEs.
12:05:32 <iwamatsu> I am reviewing 6.1.39.
12:05:45 <masami> started tracking the linux-6.1.y-cip-rt branch on cip-kernel-sec.
12:06:09 <pave1> There's a lot of patches to be applied to -cip.
12:06:42 <pave1> 1. Watchdog stuff Jan submitted -- I propose we take that one, it does not look scary and follows the rules.
12:07:09 <pave1> 2. Patches from -next submitted by Renesas -- I propose we wait there.
12:07:38 <pave1> (Waiting for patches to reach mainline before they can be applied, as usual).
12:09:02 <jki> anything else?
12:09:04 <iwamatsu> about 1 , I agree, but I suggest posting to stable first.
12:09:40 <jki> I can try that as well
12:09:51 <jki> whatever you prefer
12:10:15 <pave1> Well, I'm not sure bug is "severe enough" to meet stable rules.
12:10:44 <pave1> It is a showstopper for us, but the watchdog still works "as well as" other drivers in tree.
12:11:16 <jki> stable could argue it's a feature, but the absence of reaction from the watchdog maintainers de-motivated me to go for stable
12:13:07 <pave1> SO, lets re-evalute this one in 14 days?
12:13:27 <jki> and do nothing till then, or what now?
12:14:11 <pave1> Well, my proposal would be to just take patches and ignore the stable. It is not "clearly stable" material.
12:15:06 <pave1> If that is not acceptable, the other proposal is "jki submits it to stable, and either stable takes it or we take it after two weeks".
12:15:43 <jki> If I find some cycles, I can try the submission
12:16:19 <jki> ok, other kernel maintenance topics?
12:16:26 <jki> 5
12:16:27 <jki> 4
12:16:29 <jki> 3
12:16:31 <jki> 2
12:16:32 <jki> 1
12:16:34 <jki> #topic Kernel release status#
12:16:38 <jki> -4.4
12:16:44 <uli> no news, on track
12:17:11 <jki> -4.19
12:17:16 <iwamatsu> on track
12:17:22 <pave1> all -rt releases should be on track.
12:17:48 <jki> -5.10
12:17:54 <iwamatsu> on track
12:18:03 <jki> -6.1
12:18:30 <jki> just release... will that huge .39 delay things for us?
12:19:17 <pave1> That's usual "rc1 is huge", I don't think it should cause any issues.
12:19:34 <iwamatsu> I think so.
12:20:17 <jki> ok
12:20:27 <jki> then move on
12:20:32 <jki> #topic Kernel testing
12:21:46 <patersonc[m]> I don't have much
12:21:51 <patersonc[m]> sietze , do you have any updates on squad?
12:22:17 <sietze> Still working on a PoC for Test reporting with SQUAD
12:22:56 <sietze> We set up a test with CIP kernel testing in the CIP playground group
12:23:51 <sietze> Almost there, but unfortunately not something to show, yet
12:24:17 <jki> next week then ;-)
12:24:26 <patersonc[m]> :)
12:24:40 <sietze> Yes, I hope so, but Chris has to show it then
12:24:49 <patersonc[m]> Ha
12:24:51 <sietze> Vacation for the next 3 weeks ...
12:25:46 <jki> anything else on testing?
12:25:57 <jki> maybe you could already have a look at https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
12:26:20 <jki> there are some white fields, and maybe someone know where we are with those
12:26:38 <patersonc[m]> Okay
12:26:43 <patersonc[m]> Make it an action for me
12:26:55 <jki> ok
12:27:10 <patersonc[m]> I think all platforms are booting okay
12:27:19 <patersonc[m]> So probably Y for everything if that's what we aim to support
12:27:39 <patersonc[m]> We were originally waiting for members to say what boards they wanted to support
12:27:48 <jki> adding "T"s is a technical step, the "Y"s are the formal ones
12:28:15 <patersonc[m]> Okay
12:28:46 <jki> good, move on?
12:29:01 <jki> 5
12:29:03 <jki> 4
12:29:04 <jki> 3
12:29:05 <jki> 2
12:29:06 <jki> 1
12:29:08 <jki> #topic AOB
12:29:27 <jki> please cross-check https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#kernel_maintainership
12:30:03 <iwamatsu> ok, I will check it.
12:30:32 <jki> then I need a substitute for the next two meetings
12:30:54 <jki> I'll be back on August 10
12:30:54 <patersonc[m]> I'm away next week
12:31:34 <uli> me, too
12:31:50 <jki> who will be there next week at all?
12:32:06 <iwamatsu> o/
12:32:20 <masami> o/
12:32:39 <pave1> I'll be here. I'll do some travels in August.
12:33:36 <jki> then I would leave it up to you three if you want to sync next week
12:33:44 <jki> next but one, there will be more?
12:33:56 <jki> who would be able run that meeting?
12:34:41 <pave1> I can take the next one, and likely the one after that, too.
12:34:56 <pave1> If not, we can solve it on the next meeting :-).
12:35:26 <jki> ok, thanks!
12:35:40 <jki> other topics for today?
12:36:23 <jki> 5
12:36:24 <jki> 4
12:36:26 <jki> 3
12:36:27 <jki> 2
12:36:29 <jki> 1
12:36:30 <jki> #endmeeting