12:04:38 #startmeeting CIP IRC weekly meeting 12:04:38 Meeting started Thu Dec 1 12:04:38 2022 UTC and is due to finish in 60 minutes. The chair is iwamatsu`. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:04:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:04:38 The meeting name has been set to 'cip_irc_weekly_meeting' 12:05:17 #topic AI review 12:05:50 1. Add qemu-riscv to cip-kernel-config - patersonc 12:06:01 no updates 12:06:10 got it. thanks. 12:06:29 2. Create MR for disabling smc test in qemu - alicef 12:06:36 https://github.com/kernelci/kernelci-core/pull/1516 12:06:40 done 12:07:19 This can be closed 12:07:23 Great! 12:07:39 OK, remove from next meeting. 12:08:18 other topic? 12:08:25 3 12:08:30 2 12:08:32 we could probably also close this issue https://github.com/orgs/kernelci/projects/11 12:08:55 as I think that smc was the last problem on 4.4 12:09:07 pave1: can you confirm? 12:09:41 can we close "CIP: resolve / filter remaining issues of 4.4 branch" issue? 12:09:42 I have not watched those kernelci reports. 12:09:51 ok 12:10:03 But I guess we can close it now and reopen if neccessary. 12:10:51 ok 12:11:34 ok, move to next topic 12:11:38 #topic Kernel maintenance updates 12:11:58 i'm reviewing patches for the next 4.4-st 12:12:02 This week reported 11 new CVEs and 3 updated CVEs. 12:12:38 I did reviews on 5.10.156 and 157. 12:12:45 And some 4.4.x maintainance. 12:13:01 I reviewed 5.10.156 12:14:12 and I released cip kernels. 12:14:14 iwamatsu: "extcon: adc-jack: Fix incompatible pointer type warni..." -- I'll go ahead and apply it to 4.4.y-cip? 12:14:39 pave1: yes, please. 12:15:12 I don't think we want to do extra 4.4-cip and 4.4-cip-rt releases just for this, but we can ask Jan next time. 12:15:37 Would it be possible to copy the two configs from 4.4-cip-rt to 4.4-cip, so that bugs are caught early? 12:16:58 (And preferably test them for 4.9-stable, too.) 12:17:55 It's not a big problem, but I propose to release. 12:19:28 about copy to config: Probably it is possible. 12:20:20 s/copy to/copy two/ 12:21:49 Well, release is not that much work, but doing it for single patch... 12:22:02 uli: Do you have some patches ready for 4.4.X? 12:22:36 no, not yet 12:23:15 Lets postpone decision to next week with Jan or to mailing list? We may want to do next 4.4.X early to test the process, etc. 12:23:52 OK 12:24:14 anything else to discuss? 12:24:31 3 12:24:35 2 12:24:37 1 12:24:53 #topic Kernel release status 12:25:02 4.4 12:25:40 We did the releases :-). But 4.4-rt is not up to date with latest 4.9-rt changes. 12:26:22 OK 12:26:26 They looked a bit tricky. I have some kind of backports but they probably should be reviewed more. 12:27:14 4.19 12:28:16 We should be ok with 4.19-rt and 5.10-rt 12:29:59 LTS too 12:30:53 5.10 12:31:01 same status as 4.19 12:31:21 OK, lets move next topic. 12:31:25 #topic Kernel testing 12:31:51 no updates from me other that smc and closing 4.4 issue task 12:31:52 Hello 12:32:06 hi, patersonc 12:32:31 alicef: Should we add kernelci support to build/test linux-4.4.y-st and linux-4.4.y-st-rc? 12:32:46 I guess we'd add it to build-configs-cip.yaml? 12:32:49 pavel ? 12:32:51 Yes please. 12:32:56 ok 12:33:07 I added .yml to the trees but they were removed later. 12:33:22 I can add .yml for each test, but that's kind of ... boring. 12:33:35 alicef: Do you want me to create an issue ticket? Or just go straight to an MR? 12:33:52 So if you can come up with better way, that would be great. 12:33:58 patersonc[m]: what is best for you. I have no preference 12:34:19 What is our build/test scope for -st? The usual CIP configs? Or the usual "stable" configs that kernelci uses? 12:34:38 Perhaps cip only if that's all we're promising to maintain? 12:34:50 "stable" configs, please. They will only work on 2 of 3 boards. 12:35:13 There's board supported by 4.4-cip not supported by 4.4-st, so it would fail all the time. 12:35:52 Presumably we don't want to test for all architectures though? 12:35:58 And actually... testing -st-rt would not be bad either. 12:36:41 I'd start with all architectures. If it is too much work to maintain, we can scale back. 12:36:48 There only seems to be a linux-4.4.y-st-rt-rebase, not an linux-4.4.y-st-rt? 12:37:04 I have ti locally. I'll push it. 12:37:26 But it will have same data as -st-rebase. 12:37:42 Thanks 12:37:55 What is the expected update frequency for the -st branches? 12:38:49 Less than once in 14 days, unless we are debugging something. -st-rc might be a bit more often. 12:38:59 OKay 12:39:13 Thank you! 12:39:14 :-) 12:40:30 anything else? 12:40:32 I've no other topics to raise 12:40:58 ok 12:40:59 3 12:41:01 2 12:41:03 1 12:41:19 #topic AOB 12:42:31 Is anyone going to OSS-J in person next week? 12:43:09 I'd like to visit Japan one day, but not next week. 12:43:25 I am going to participate. 12:44:07 I'll be there if anyone wants to meet up 12:46:12 Kobayashi-san may be thinking about meetup. I will ask him. 12:46:44 pave1: That’s a shame. 12:47:03 anyone anything else for today? 12:47:09 3 12:47:12 2 12:47:15 1 12:47:26 #endmeeting