09:00:03 #startmeeting CIP IRC weekly meeting 09:00:03 Meeting started Thu Jun 20 09:00:03 2019 UTC and is due to finish in 60 minutes. The chair is szlin. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:03 The meeting name has been set to 'cip_irc_weekly_meeting' 09:00:13 #topic rollcall 09:00:22 hi 09:00:23 please say hi if you're here 09:00:25 hi 09:00:25 hi 09:00:51 hi 09:00:52 hi 09:01:05 #topic AI review 09:01:11 hi 09:01:15 hi 09:01:16 1. Send investigating email for kernel-testing lab to cip-dev - patersonc 09:01:50 I think we can remove this action. I've created requirements for the lab and sent them to a vendor for quote. 09:02:03 When I know more about costs I'll update the TSC 09:02:05 patersonc: thanks. 09:02:28 2. Provide the script for CIP kernel config collection - bwh 09:02:57 This is nearly ready. I will push it to Gitlab shortly. 09:03:21 bwh: thanks. 09:03:33 3. List some questions to ask Daniel Wagner - szlin 09:03:54 This AI is still ongoing, 09:04:13 Ok, let me chime in. 09:04:29 I took a look at -cip-rt tree... and it is scary, but not that scary. 09:05:07 I guess best course of action is to simply try updating -cip-rt to 4.19.50, and gather any questions that arise while doing that. 09:05:13 hi 09:05:33 Would it be ok for me to try that? 09:05:49 no objection here 09:06:00 iwamatsu: bwh any comments? 09:06:12 No 09:06:51 pave1: ok 09:07:17 #action Update CIP RT kernel to 4.19.50 - Pavel 09:07:28 I guess I'll have some (stupid) questions about rt after the meeting, if interested parties could stay for a while after that... 09:07:45 pave1: please keep us posted after the updating :-) 09:07:46 szlin: I'd formulate that as "Try updating", but ok ;-). 09:08:07 pave1: I see 09:08:39 #topic Kernel maintenance updates 09:09:50 iwamatsu: pave1 bwh do you have any updates on kernel maintenance updates? 09:09:59 szlin: I released 4.4.181-cip33 and 4.19.50-cip3, and I reviewed v4.4.161 and v4.4.162. 09:10:20 I reviewed 4.19.51 and 4.19.53. 09:10:25 iwamatsu: thank you for your work. 09:10:31 pave1: thank you! 09:10:44 There was question on the mailing list: 09:10:57 4.19.52 contains fixes for remote crash. 09:11:11 It might be worth doig out-of-cycle updates to incorporate that 09:11:14 It is just a crash, but it got wide publicity. 09:11:17 Exactly. 09:11:58 pave1: I already upldated to lastet kernel in my local repo. 09:12:57 Jan raised a question in SACK issue 09:13:00 iwamatsu: If that's okay with you, I believe releasing it soon would make sense. 09:13:02 #info https://lists.cip-project.org/pipermail/cip-dev/2019-June/002496.html 09:13:25 I can release new cip kernel soon to fix SNAK issue. 09:13:59 pave1: OK, I will release after this meeting 09:14:14 iwamatsu: thank you very much. so this new release will be at next Friday? 09:16:27 iwamatsu: it's ok to reply me after the meeting 09:16:38 any other topics? 09:16:46 3 09:16:46 2 09:16:47 1 09:16:57 #topic Kernel testing 09:17:12 Hello 09:17:16 Issues with LAVA master (login issues, email notification issues) have been resolved. 09:17:21 I'm not sure if Mentor have made any more progress on their lab, I'll check. 09:17:26 LF are still working out if/how they can give us SSH access to the LAVA master. 09:17:38 Questions: 09:17:41 Regarding Renesas RZ/G boards, what maintainers already have access to a physical board? 09:17:43 And do any maintainers need a physical board if they don't already have one? 09:17:47 Is remote access using LAVA enough for maintenance needs? 09:18:35 patersonc: do you mean "kernel" maintainer ? 09:18:44 Yes, sorry 09:19:21 Basically I want to know if Renesas needs to provide any more boards 09:19:35 No access, but I don't think I urgently need one. You are providing patches and testing, so there's not much development I need to do there 09:20:04 pave1: Okay. Thank you. 09:20:38 bwh: iwamatsu: ^ do you have any comments? 09:20:44 No 09:21:06 I dont have any comment. 09:21:21 thanks. 09:21:25 Okay 09:21:26 any other topics? 09:21:26 I guess that's it from me, unless there are any questions? 09:21:53 3 09:21:54 2 09:21:55 1 09:22:02 #topic CIP Core 09:22:17 kazu_: give the floor to you 09:22:27 Hello 09:22:35 Held the second CIP-Core meeting to discuss the package decision process 09:22:41 There are topics remaining that should be discussed more 09:23:04 I'm clarifying the action items, then will report the summay to CIP members ML 09:23:17 today or tomorrow 09:23:56 kazu_: thanks, have you decided to have CIP-core F2F meeting in OSS-J? 09:24:17 Sorry, not yet 09:24:36 I would like to propose this topic to the ML as well 09:24:48 kazu_: got it, please keep us posted if you make the decision :) 09:25:06 Thank you 09:25:17 any other topics? 09:25:20 3 09:25:22 2 09:25:23 There are several technical updates from Daniel, but he doesn't attend ? 09:25:48 kazu_: yes, he is not here 09:26:06 OK, please go ahead 09:26:10 1 09:26:21 #topic Software update 09:26:47 kazu_: since Daniel is not here, would you like to update this topic? 09:28:00 or he can update these topics via cip-dev afterwards 09:28:09 Sorry, I don't summarize the updates of this topic... 09:28:18 kazu_: never mind :) 09:28:21 I think so 09:28:25 any other updates? 09:28:27 3 09:28:28 2 09:28:29 1 09:28:31 #topic AOB 09:28:35 any other business? 09:28:48 3 09:28:49 2 09:28:50 1 09:29:07 #endmeeting