09:00:02 #startmeeting CIP IRC weekly meeting 09:00:02 Meeting started Thu May 27 09:00:02 2021 UTC and is due to finish in 60 minutes. The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:02 The meeting name has been set to 'cip_irc_weekly_meeting' 09:00:05 #topic rollcall 09:00:13 please say hi if you're around 09:00:13 hi 09:01:07 Let's get started. 09:01:10 #topic AI review 09:01:18 1. Combine root filesystem with kselftest binary - iwamatsu 09:01:19 hi 09:01:36 iwamatsu: are you around? 09:01:53 Let's come back after he joins. 09:01:54 2. Do some experiment to lower burdens on CI - patersonc 09:02:12 No updates 09:02:19 patersonc: Sure, thanks. 09:02:22 hi 09:02:33 3. Monitor the status of CVE-2021-3444 and CVE-2021-20292 (3/25) - Kernel Team 09:02:33 4. Monitor the status of CVE-2021-29650 (4/1) - Kernel Team 09:02:49 pave1: Do you have any update on 4? 09:03:07 Not much progress, overwhelmed with reviews, sorry. 09:03:18 pave1: Noted. Thanks! 09:03:29 Let's move on. 09:03:33 5. Update Testing table below with 5.10 info - patersonc 09:03:48 patersonc: Do you have update on this? 09:04:13 Nope. Sorry! 09:04:27 patersonc: Note. Thanks. 09:04:40 sorry, I"m late. 09:04:51 iwamatsu: Hi, do you have any update on AI#1? 09:05:00 no update. 09:05:21 iwamatsu: Noted. Thanks. 09:05:26 Let's move on. 09:05:35 #topic Kernel maintenance updates 09:05:46 ===== CVE status this week ===== 09:05:47 No actionable items for CIP: issue is fixed completely, or patch is still waiting to be queued up. 09:05:47 ======================= 09:06:04 Reviews: 5.10.38, 39 and 40. 09:07:04 iwamatsu: Do you have updates? 09:07:17 I reviewed 4.4.270 09:07:50 pave1, iwamatsu: Thanks for your updates. 09:08:05 any other topics? 09:08:10 3 09:08:14 2 09:08:17 1 09:08:20 #topic Kernel testing 09:08:28 patersonc: The floor is yours. 09:08:48 I'm not sure I have anything to share. 09:09:10 alicef: How is the kselftest work going? 09:09:37 hi patersonc 09:10:08 I could build kselftest binary for arm arm64 09:10:34 and the linux-cip-ci pipeline worked correctly 09:10:59 nice 09:11:27 :) 09:11:44 alicef: That's great! Is it local? Can you upload the changes? 09:12:00 I'm now trying to test it with linux-cip-pipelines and linux-stable-rc-ci 09:12:55 patersonc: can I make branch for testing it with other cip ci pipelines ? 09:13:19 gitlab pipeline 09:13:24 Sure. Let's chat after this meeting 09:13:49 patersonc, alicef: Thanks. 09:14:02 patersonc: I'm in the process to clean a bit the code and send the new pull request 09:14:21 masashi910: the code is here https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/tree/alicef/kselftests 09:14:39 and here https://gitlab.com/cip-playground/cip-kselftest/ 09:14:48 alicef: Thanks for your works! 09:15:07 any other topics? 09:15:14 3 09:15:17 2 09:15:20 1 09:15:23 #topic AOB 09:15:29 I have one item to discuss. 09:15:43 Regarding IRC meetings, I am thinking to leave for other IRC server. 09:16:00 Does anybody have any opinios? 09:16:03 I don't care much as long as we stay on IRC. 09:16:14 :) 09:16:31 Most people seem to be moving to l i b r e chat 09:16:48 Lets say it loud and force the move? :-) 09:16:49 a number of channels were seized already. #cip is the last channel that kept me stick around 09:17:00 yes most project moved to libre.chat 09:17:13 I believe the issue is that freenode may want to prevent the move. 09:17:16 also #kernelci moved to libre.chat 09:17:28 iwamatsu: do you have any opinion? 09:17:33 I am fine on which server. 09:17:47 Thanks for all your comments! 09:18:02 if you put that other network in the topic or apply +m, a bot will take over the channel 09:18:23 So the first step would be updating topic here to point to some webpage we control, and where we can point people to new network. 09:18:40 that's unfortunatly happened to many channels 09:19:07 So, I would like to use libre.chat. 09:19:14 there is a document about how to do it properly 09:19:59 Next week, let me host this meeting by using a new server. 09:20:12 alicef: Please help me! 09:20:43 masashi910: sure 09:20:52 alicef: Thanks! 09:20:55 Are there any business to discuss? 09:21:06 5 09:21:08 about release of 5.10.y-cip 09:21:33 We have not yet released because we do not have a patch from CIP members for this kernel. 09:21:45 Do we need to wait for this? 09:22:04 I have list of patches that are in 4.19-cip but not in 5.10-cip. 09:22:37 We have to wait for the final decision of CIP TSC. 09:22:41 I suggest that we will release regularly as a CIP kernel as well as another CIP kernels. 09:22:54 There's ~200 of them AFAICT. 09:22:55 masashi910: I see. 09:23:34 iwamatsu: Thanks for your patience. 09:23:37 So I guess it would be better to push the submitters. 09:23:38 I understood current status. 09:24:09 pavel: I think so. 09:24:15 pave1: I know a lot of them are Renesas', I'm just a bit busy atm :( 09:24:56 pave1: Yes, we have to prepare for the release. So let's advise them. 09:25:10 pave1: We're currently upstreaming a new device. Once done we'll backport it to 5.10 and get 4.19 in sync at the same time 09:25:25 pavel: if you can share it to me / us, I can support it. 09:25:36 iwamatsu: Ok, will do. 09:25:59 pave1: thanks. 09:26:06 Thanks for this discussion. Any other topics? 09:26:20 4 09:26:26 3 09:26:31 2 09:26:35 1 09:26:38 So, let's close today's meeting. 09:26:44 #endmeeting