13:03:16 <jki> #startmeeting CIP IRC weekly meeting
13:03:16 <collab-meetbot`> Meeting started Thu Feb  2 13:03:16 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:03:16 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:03:16 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:03:23 <jki> #topic AI review
13:03:34 <jki> - enable more stable trees for testing (patersonc)
13:03:48 <jki> chris is not around, so skip
13:03:55 <jki> anything else?
13:06:43 <jki> 3
13:06:43 <jki> 2
13:06:43 <jki> 1
13:06:43 <jki> #topic Kernel maintenance updates
13:06:58 <uli> i reviewed 5.10.164
13:07:04 <masami> This week reported 4 new CVEs and 3 updated CVEs.
13:07:07 <pave1> I'm reviewing 5.10.166, .167.
13:07:19 <pave1> I'm preparing for 4.4-rt update.
13:10:54 <jki> pavel: uli is looking over your shoulder during that, right?
13:12:14 <pave1> Not at the moment. It looks like we'll want to review pending patches together, but there's nothing critical in the pending list,
13:12:42 <pave1> so I'll simply release rebased version.
13:13:20 <pave1> It is "git merge" and "git rebase" when it works, there's not really much to look at :-)
13:13:29 <jki> ok, that means you will continue doing that step also for future releases?
13:13:44 <jki> I also noticed that iwamatsu did the 4.4 release announcement - missing access for uli?
13:14:03 <pave1> My understanding is that uli will do that at some point but not right now...?
13:14:30 <uli> i assumed that was the standard procedure; i can do it myself from now on
13:14:49 <pave1> Iwamatsu was doing all the -cip releases, so we kind of assumed it was supposed to work like that.
13:15:16 <jki> in the end, it is about workload sharing but also having redundancy in the process when we need to release and someone is not available
13:20:08 <jki> so, continue running in most efficient mode is fine if the latter is also ensured
13:20:38 <jki> but maybe revisit this when iwamatu is around as well
13:20:48 <pave1> I believe we have enough access to do the -cip releases if we needed, but it was not needed so far :-).
13:20:59 <jki> anything else?
13:21:52 <jki> 3
13:21:54 <jki> 2
13:21:56 <jki> 1
13:21:59 <jki> #topic Kernel release status
13:22:06 <jki> - 4.4
13:22:11 <uli> 4.4.302-cip72 is out
13:22:26 <pave1> I'm looking at 4.4-rt.
13:22:39 <jki> fine (just a bit delayed ;) )
13:22:46 <jki> - 4.19
13:23:34 <jki> everyhing should be up-to-date - any issues ahead?
13:23:50 <pave1> Nothing I'm aware of.
13:24:04 <jki> - 5.10
13:25:41 <jki> looks like the same
13:26:15 <jki> anything else?
13:26:30 <jki> 3
13:26:32 <jki> 2
13:26:33 <jki> 1
13:26:35 <jki> #topic Kernel testing
13:26:39 <alicef> sent pull request for using cip-kernel-configs for 5.10.y-cip kernel on kernelci, added also riscv config https://github.com/kernelci/kernelci-core/pull/1705
13:29:33 <jki> I added "status 6.1 LTS testing call of Greg" to the agenda
13:29:41 <jki> did we do anything in this regard?
13:30:45 <alicef> not on my knowledge
13:31:15 <jki> are we testing 6.1 by now? or is that the AI from above?
13:31:36 <alicef> i will check with patersonc[m]
13:31:47 <jki> what else would be missing to speak up in that thread?
13:36:55 <pave1> Even something as simple as running tests once with 5.10.X configs would be quite helpful.
13:37:31 <alicef> kernelci will start doing that for 5.10
13:37:54 <pave1> I meant test 6.1.X on our boards with 5.10.X configs.
13:37:54 <jki> exactly, and once we do that, we should drop a note to motivate Greg a bit more
13:38:38 <alicef> i see
13:39:21 <pave1> (Or if you can read the kernelci results and say "hey, according to kernelci it works ok on cip boards.. would be also helpful).
13:40:58 <jki> anything else on testing?
13:41:59 <jki> 3
13:42:01 <jki> 2
13:42:03 <jki> 1
13:42:05 <jki> #topic AOB
13:42:29 <pave1> There was query about 4.9 on the mailing list. I don't think we want to do that, but... :-)
13:42:51 <jki> was nicely answered, yes :)
13:44:16 <jki> does anyone know who is Dan Carpenter, and why cip is so often CC'ed now?
13:44:48 <jki> nice to be recognized, was just wondering
13:45:27 <pave1> He's long time linux contributor, I have Dan Carpenter <dan.carpenter@oracle.com> in my records.
13:45:43 <pave1> But not sure what he has to do with CIP.
13:47:24 <jki> ok - anything else?
13:50:12 <jki> 3
13:50:13 <jki> 2
13:50:15 <jki> 1
13:50:20 <jki> #endmeeting