12:01:18 #startmeeting CIP IRC weekly meeting 12:01:18 Meeting started Thu Jun 30 12:01:18 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:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:01:18 The meeting name has been set to 'cip_irc_weekly_meeting' 12:01:23 hello everyone! 12:01:29 Hi 12:01:34 hello 12:01:42 Hello 12:01:50 hello 12:02:11 hi 12:02:33 hi 12:03:30 let's go! 12:03:35 #topic AI review 12:03:41 1. Provide ignore-list for failures of KernelCI on 4.4-cip - pavel 12:04:35 I went through the bugs for an hour, and could not find a 'good' one. 12:04:54 I sent the findings to the list, but no reply so far. 12:05:19 alicefm: did you have a chance to look at that? 12:06:35 Not yet. 12:07:23 ok, then I would assign the AI back to you 12:07:55 2. Check cip devices on kernelci old pull request - patersonc 12:09:30 No further progress this week 12:09:55 3. Update https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware - iwamatsu-san 12:10:16 No update yet. 12:10:35 ok, other AIs? 12:10:56 3 12:10:57 2 12:11:00 1 12:11:05 #topic Kernel maintenance updates 12:11:26 I did reviews on 5.10.127. 12:11:28 reviewed 5.10.125 12:11:33 This week reported no new CVEs and 5 updated CVEs 12:11:43 I'm working on moving 4.4 forward. 12:11:44 I reviewed 5.10.125,126 12:12:21 4.19 and 5.10 need rt releases, it would be nice to coordinate -cip releases with them. 12:13:26 I'll be traveling next week, so will not make it to Tuesday's call. 12:13:54 Yes, the timgin is not match.... 12:14:43 Yep, the -rt releases are not too frequent .-( 12:15:38 pavel: do you get indications when the next one will come? 12:15:47 are you on that maintainer call as well? 12:16:26 I did not make it to the last one, but normally I'm invited, yes. 12:17:00 No indications other than history. 12:17:21 They are about month apart AFAICT. 12:17:59 then all we could do is to schedule an extra cip release to account for cip-rt 12:18:01 right? 12:19:54 Well, or we can delay a release to get a match .-) 12:20:32 if that is possible... 12:20:43 In that case, we will not be able to release every two weeks. 12:21:20 worst case: delay by two weeks - right 12:21:45 classic issue of two unsynchronized cyclic tasks 12:21:49 That should work. 12:22:24 Dunno. If releases are easy to do for iwamatsu-san, we can simply keep doing extra ones. 12:24:00 hehe 12:24:26 First , why not try it experimentally? 12:26:55 iwamatsu: what do you mean exactly? what should we do next in this case? 12:29:19 sorry, the experiment will be a normal release and a CIP kernel release to coincide with the RT release. 12:30:30 so, wait for the next -rt releases, then to an extra cip, then the cip-rt ones, right? 12:30:52 pavel: fine for you? 12:31:00 Yes 12:31:05 Yes, that should work. 12:31:19 perfect 12:31:38 pavel: you will ping iwamatsu-san? 12:32:02 I am checking RT release, too. 12:32:06 Ok, will do so once suitable 4.19-rt or 5.10-rt is released. 12:32:25 great 12:32:33 move on? 12:32:50 3 12:32:50 Yes. 12:32:52 2 12:32:53 1 12:32:57 #topic Kernel testing 12:34:34 Sorry, my IRC got disconnected 12:34:46 I'm not sure there are a huge amount of updates from last week 12:35:08 Iwamatsu-san, have you heard anything from Plat'home about that cip-kernel-config MR for their board? 12:35:56 I am waiting MR from Minda-san yet. 12:36:43 I will send ping to him. 12:37:45 Thanks 12:39:29 anything else? 12:39:41 Not from me 12:39:52 3 12:39:54 2 12:39:57 1 12:40:00 #topic AOB 12:42:40 nothing? 12:42:49 3 12:42:51 2 12:42:54 1 12:42:57 #endmeeting