12:02:53 <jki> #startmeeting CIP IRC weekly meeting
12:02:53 <collab-meetbot> Meeting started Thu Oct 19 12:02:53 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:53 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:02:53 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
12:03:02 <jki> #topic AI review
12:03:10 <jki> none recorded
12:03:19 <uli> hello
12:03:41 <jki> #topic Kernel maintenance updates
12:04:01 <uli> i reviewed 6.1.55
12:04:20 <pave1> Reviewing 6.1.59.
12:05:34 <pave1> uli: There's rather quiet period with reviews at the moment, but I guess there'll be next batch soon.
12:05:51 <uli> that suits me well atm
12:06:09 <pave1> Ok, good :-).
12:07:29 <jki> anything else?
12:08:04 <jki> 5
12:08:05 <jki> 4
12:08:07 <jki> 3
12:08:08 <jki> 2
12:08:09 <jki> 1
12:08:11 <jki> #topic Kernel release status
12:08:14 <jki> 4.4
12:08:18 <uli> on track
12:08:21 <pave1> I should do -rt.
12:08:55 <jki> 4.19
12:09:16 <pave1> 4.19-rt, 5.10-rt are on track for another month.
12:10:15 <jki> regular is due end of this month
12:10:16 <jki> ok
12:10:19 <jki> 5.10
12:10:56 <jki> regular is due now
12:11:17 <jki> let's check again next week
12:11:22 <jki> 6.1
12:11:50 <jki> regular just released - how about -rt?
12:12:03 <pave1> -rt is due in few days; but last one is v6.1.54-rt15 so I'd really like newer one.
12:13:23 <jki> anything on the way in upstream?
12:14:08 <pave1> No idea. -rt's usually don't have release candidates.
12:15:11 <jki> maybe ping them
12:15:22 <jki> ok, then move on
12:15:28 <jki> #topic Kernel testing
12:16:08 <patersonc> Hello
12:16:39 <patersonc> Our LAVA server and labs are now all upgraded to LAVA v2023.08
12:16:41 <patersonc> At last
12:16:48 <patersonc> Things seems to be working okay so far
12:17:10 <patersonc> Siemens have been working on relocating their lab. The new lab is up and running with a qemu machine. Boards will be added soonish
12:17:21 <arisut> waiting for guilleam to check my PR https://github.com/kernelci/kernelci-core/pull/2123
12:17:48 <arisut> as by kernelci rule I cannot merge my own PR
12:18:34 <jki> can't patersonc? ;)
12:18:41 <patersonc> nope
12:19:45 <patersonc> I've added gctucker as a reviewer now. Maybe he'll pick it up soon
12:20:08 <patersonc> I've not much else for testing topics
12:20:09 <jki> further test topics?
12:20:45 <jki> 5
12:20:47 <jki> 4
12:20:48 <jki> 3
12:20:50 <jki> 2
12:20:51 <jki> 1
12:20:53 <jki> #topic AOB
12:21:09 <pave1> arekm: Are you around?
12:21:20 <pave1> In irc logs, I have noticed 4.4 bug reports from arekm.
12:21:29 <uli> he has contacted me by mail since
12:21:53 <patersonc> https://ircbot.wl.linuxfoundation.org/logs/%23cip/%23cip.2023-10-18.log.html
12:22:02 <uli> it's about 3 patches that need to be reverted
12:22:11 <pave1> Aha, good. It would be nice to get cip-dev in cc list.
12:22:26 <uli> i asked him to send reports to cip-dev in the future
12:22:46 <pave1> Yep.Would it be possible to get more .configs for at least build tests?
12:22:50 <jki> there was also some powerpc build fix - some guy?
12:23:00 <patersonc> On a related topic - we should try and have some maintainers sitting on #cip-dev to reply to such comments if possible - obviously timezones will affect things a bit
12:23:01 <uli> pave1: i asked for those, too; he sent them to me
12:23:43 <pave1> uli: That was more question for q&a. It looks we may want to start to do more of the testing, because we are no longer supported by -stable team and their testers.
12:23:50 <pave1> jki: Name sounds different.
12:24:35 <uli> i just saw the ppc patch; that's a different person
12:25:17 <jki> looks like easy to add, even while we do not commit to ppc
12:25:49 <uli> should be no problem
12:26:31 <patersonc> Do we add the config to cip-kernel-configs? Or to a different repo? (or a different "unofficial" branch)
12:26:31 <jki> and, how about promoting also our new tarball downloads in the release emails?
12:26:41 <pave1> If we get more ppc patches we may start asking "what are you doing with it".
12:26:47 <jki> I saw someone asking for it in the lwn.net comments
12:27:23 <pave1> jki: Hmm. Reminds me I probably need to sign 4.19-rt to get the tarball out. Another for todo list.
12:27:28 <jki> yes, maybe clarify that ppc is not officially supported when merging and saying "thanks"
12:27:47 <jki> pavel: yes, that is important
12:27:56 <jki> we can't update our build recipes without it
12:28:32 <pave1> Adding a note "tarball should appear shortly at" would not be hard for me.
12:28:50 <uli> +1
12:29:11 <pave1> Actually waiting and verifying the tarball would add one more wait for external machines.
12:29:43 <jki> plus adding a link to that email, maybe only to the folder
12:30:10 <jki> delaying the email may cause forgetting to send it, I could imagine ;)
12:30:50 <pave1> jki: Linking only to the folder sounds like good idea :-).
12:31:35 <jki> anything else for today?
12:32:47 <jki> 5
12:32:49 <jki> 4
12:32:50 <jki> 3
12:32:51 <jki> 2
12:32:53 <jki> 1
12:32:56 <jki> #endmeeting