09:00:02 <masashi910> #startmeeting CIP IRC weekly meeting
09:00:02 <brlogger`> Meeting started Thu Dec 19 09:00:02 2019 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 <brlogger`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:02 <brlogger`> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:14 <masashi910> #topic rollcall
09:00:21 <pave1> hi
09:00:24 <masashi910> please say hi if you're around
09:00:24 <kazu> hi
09:00:27 <iwamatsu> hi
09:00:28 <suzuki90> hi
09:00:29 <wens> hi
09:00:40 <patersonc> hi
09:00:43 <masashi910> #topic AI review
09:00:51 <masashi910> 1. Test LTS (pre)releases directly - patersonc
09:01:10 <patersonc> Hello
09:01:19 <masashi910> Chris-san, hi!
09:01:42 <masashi910> Chris-san, do you have updates?
09:01:43 <patersonc> I've now improved the way the commits we test are shown in GitLab
09:01:56 <patersonc> e.g. https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines
09:02:05 <patersonc> It's now clear which commit is tested
09:02:32 <patersonc> Last 2 things remaining are to merge the PRs, and move everything to the cip-testing project
09:02:57 <masashi910> patersonc: thanks! OK, shall we keep this AI open?
09:03:20 <patersonc> Yes please
09:03:25 <patersonc> Getting there...
09:03:34 <masashi910> patersonc: sure!
09:03:37 <masashi910> 2. Create a way/process to run LTP only for release tests - patersonc
09:03:52 <masashi910> patersonc: do you have updates on this?
09:03:53 <patersonc> Process has been proposed, MRs are submitted
09:04:04 <patersonc> I just need to document the process on the Wiki and merge
09:04:17 <patersonc> (process was also agreed by maintainers)
09:04:29 <patersonc> Feel free to keep this open
09:04:44 <masashi910> patersonc: thanks for your progress! then, shall we keep this AI open as well?
09:05:02 <patersonc> Yep
09:05:13 <masashi910> patersonc: OK!
09:05:14 <masashi910> 3. Combine rootfilesystem with kselftest binary - Iwamatsu-san
09:05:31 <masashi910> Iwamatsu-san, do you have updates on this?
09:05:47 <iwamatsu> masashi910: No update.
09:05:52 <iwamatsu> please keep this A.I.
09:06:18 <masashi910> iwamatsu: thanks for your report. Sure, I will keep this ai open.
09:06:27 <masashi910> 4. Document a process on how to add tests to the CIP test setup - patersonc
09:06:38 <patersonc> No progress
09:06:55 <masashi910> patersonc: thanks for your report!
09:07:04 <masashi910> 5. Arrangement of F2F Kernel Meeting in Nurnberg - masashi910
09:07:13 <masashi910> I set up a doodle poll last week.
09:07:22 <masashi910> So far, only Chris-san responded to this. I would like to report the result to TSC tomorrow. So, please fill your availability to the poll.
09:07:29 <masashi910> https://doodle.com/poll/73if9scwqrh5ge38
09:07:48 <masashi910> then, let me move to next.
09:07:54 <patersonc> 0/
09:07:59 <masashi910> #topic kernel maintenance updates
09:08:12 <patersonc> There is a chance I'll only be attending EW remotely, depending on budget.
09:09:03 <masashi910> patersonc: I see. If the meeting is set up, I will also set up the zoom channel.
09:09:23 <patersonc> masashi910: Thanks
09:10:02 <masashi910> pave1, iwamatsu, wens, bwh: do you have any updates?
09:10:06 <wens> classify-failed-patches will now (pending merge request) include stable patch review series from Greg. there are still some patches that are left out due to random tags. I'll add these as I find them.
09:10:33 <wens> I assume people likely don't want Sasha's AUTOSEL series to be included though
09:10:52 <pave1> I did reviews on 4.19.89 and 1.19.90, and am now in progress of merging of "Add RZ/G2N SYSC/RST/Clock/PFC support" series.
09:11:01 <iwamatsu> I review LTS-rc on stable ML, I send some comment.
09:11:18 <wens> cip-kernel-sec gained (pending MR) four new CVEs, one is fixed, three (as of commit time) are not
09:12:02 <pave1> wens: Yes, excluding autosel stuff should save a lot of work.
09:12:51 <masashi910> wens, pave1, iwamatsu: thanks for your works!
09:13:00 <wens> there's also a new make target that will show mails that are probably patches but aren't included
09:13:04 <pave1> wens: Could we talk after the meeting?
09:13:10 <wens> pave1: sure
09:13:19 <patersonc> o/
09:13:24 <masashi910> wens, pave1: thanks!
09:13:37 <masashi910> any other topics?
09:13:51 <masashi910> 3
09:13:56 <masashi910> 2
09:13:59 <masashi910> 1
09:14:02 <patersonc> yes
09:14:03 <masashi910> #topic Kernel testing
09:14:12 <patersonc> Just to let you all know, Biju and Fabrizio will be leaving Renesas tomorrow, so you'll see a dramatic drop in patches coming from them :)
09:14:33 <patersonc> If there is any feedback you need on patches etc. before then, it may be worth asking today
09:14:36 <patersonc> Sorry for the short notice
09:14:43 <pave1> patersonc: They will be missed...
09:14:52 <patersonc> pave1: Very much so!
09:15:22 <masashi910> patersonc: I see. Thanks for sharing this info. And please send our best regards to them for their contributions!
09:15:31 <patersonc> I will
09:15:38 <masashi910> patersonc: the floor is yours
09:15:58 <patersonc> Back to CIP testing...
09:16:03 <patersonc> As reported earlier I've been improving the LTS stable-rc build/testing process
09:16:15 <patersonc> Pretty much done now, just need to merge and move the project to cip=testing
09:16:32 <patersonc> I've also been working on setting up LTP testing for '-rc' branches
09:16:53 <patersonc> The Mentor lab/boards are back online after some lab maintenance last weekend
09:17:20 <patersonc> I'll merge CI support for them soon, but there is a worry that the internet connection is randomly very slow
09:17:29 <patersonc> Which can cause jobs to fail, often
09:17:52 <patersonc> I think that's about it from me. Any queries?
09:18:20 <masashi910> patersonc: thanks for your works!
09:18:59 <patersonc> No worries
09:19:08 <masashi910> does anybody have any questions, or any other topics?
09:19:20 <masashi910> 3
09:19:24 <masashi910> 2
09:19:28 <masashi910> 1
09:19:31 <masashi910> #topic CIP Core
09:19:39 <kazu> hello
09:19:42 <masashi910> kazu: the floor is yours
09:19:45 <kazu> 1. PDP: Package review on-going, please start discussions about specific packages if you need
09:20:10 <kazu> I'm a bit worrying no discussion about the packages :)
09:20:17 <kazu> 2. Just started https://gitlab.com/cip-project/cip-core/deby/issues/4; use the existing configs for kernel builds
09:20:30 <kazu> I would like to ask one question about this later
09:20:39 <kazu> 3. In-progress https://gitlab.com/cip-project/cip-core/deby/issues/7; still checking and reusing the old script to submit tests to LAVA: https://gitlab.com/cip-project/cip-core/deby/blob/master/poky/scripts/lava-submit-job.sh
09:21:01 <kazu> I will focus on this in this month
09:21:10 <kazu> That's all from me, any question?
09:21:23 <masashi910> kazu: regarding 2, "I would like to ask one question about this later", do you mean after the call?
09:21:38 <kazu> sorry, in AOB is better
09:21:48 <patersonc> kazu: Do CIP plan to support all of the dependency patches long-term? Or just the requested packages?
09:21:53 <masashi910> kazu: I see.
09:22:42 <kazu> patersonc sorry, what does " the dependency patches" mean here?
09:23:15 <patersonc> I think the security group requested 19(?) packages? But they require another x packages on top
09:23:34 <kazu> patersonc Yes, correct
09:23:57 <patersonc> Will we support everything long-term? Or just the 19
09:24:03 <kazu> patersonc Dependency packages will be discussed in the next step, they are now requesting the 21 packages first
09:24:12 <patersonc> Ah okay
09:24:21 <patersonc> Thanks
09:24:32 <kazu> because reviewing everything in one proposal is a bit complicated :)
09:24:57 <kazu> any other topics?
09:25:14 <masashi910> kazu: thank you!
09:25:23 <masashi910> then let's move to the next
09:25:30 <masashi910> #topic Software update
09:25:41 <suzuki90> hi
09:25:44 <suzuki90> I've put a license file of apache license 2.0 into the top of cip-sw-updates-demo repository.
09:25:49 <suzuki90> https://gitlab.com/cip-playground/cip-sw-updates-demo/blob/master/LICENSE
09:25:54 <suzuki90> And I'm preparing an approval request for creating our WG's subgroup in cip-project of Gitlab.
09:26:01 <suzuki90> That's all from me.
09:26:09 <masashi910> suzuki90: Thanks!
09:26:16 <masashi910> any other topics?
09:26:20 <masashi910> 3
09:26:21 <masashi910> 2
09:26:23 <masashi910> 1
09:26:30 <masashi910> #topic AOB
09:26:37 <masashi910> 1. IRC meeting next week
09:26:48 <masashi910> Although it is a holiday season, I would like to hold an IRC meeting next week.
09:27:05 <masashi910> 3
09:27:06 <masashi910> 2
09:27:07 <masashi910> 1
09:27:13 <kazu> hi
09:27:22 <masashi910> kazu: please
09:27:22 <kazu> can i ask one?
09:27:25 <patersonc> I'll be missing the meeting for the next 2 weeks
09:27:44 <masashi910> patersonc: OK, thanks for letting me know.
09:27:52 <kazu> I'm checking the existing kernel configs for each CIP reference hardware, the following understanding correct?
09:28:01 <kazu> Available configs: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/tree/master/4.19.y-cip/
09:28:04 <pave1> So Dec 26? Not sure if I'll be able to make that one.
09:28:09 <kazu> Used configs: https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/blob/master/trees/linux-4.19.y-cip.yml
09:28:26 <kazu> qemux86-64: (no config?)bbb: (no config?)iwg20m: renesas_shmobile_defconfigsimatic-ipc227e: ?OpenBlocks IoT: plathome_obsvx2.confighihope-rzg2m: renesas_defconfig
09:28:40 <kazu> Oops, will add one by one...
09:28:43 <patersonc> I think that's correct
09:28:47 <kazu> qemux86-64: (no config?)
09:28:52 <kazu> bbb: (no config?)
09:28:57 <kazu> iwg20m: renesas_shmobile_defconfig
09:29:00 <masashi910> pave1: thanks. No worries.
09:29:05 <kazu> simatic-ipc227e: ?
09:29:12 <kazu> OpenBlocks IoT: plathome_obsvx2.config
09:29:16 <kazu> hihope-rzg2m: renesas_defconfig
09:30:00 <kazu> I just want to confirm if there are configs for qemux86-64 and bbb or not...
09:30:17 <patersonc> No that I've seen
09:30:28 <patersonc> If they are added I'll start building them in CI :)
09:30:47 <iwamatsu> kazu: I have a config to qemu-x86-64. so I will send PR to config repo.
09:30:51 <pave1> Do we have qemu/bbb configured so that it could be used for testing if we hav ethe configs?
09:31:02 <patersonc> Or if someone points me to a suitable config elsewhere/intree
09:31:19 <patersonc> pave1: qemu - yes. BBB - maybe e/Jan
09:31:24 <kazu> patersonc iwamatsu Thank you
09:31:33 <patersonc> We can build without the boards in the lab though
09:32:29 <masashi910> kazu, patersonc, iwamatsu, pave1: thanks for your discussion.
09:32:33 <pave1> patersonc: Yes, agreed.
09:32:46 <masashi910> kazu: do you think any AI needed?
09:33:35 <kazu> At least, the config for qemux86-64 will be added through the PR?
09:34:11 <patersonc> Agreed. And a config for BBB would be good too.
09:34:32 <iwamatsu> OK, I ask BBB config to Jan.
09:34:33 <patersonc> For both boards, I think we need a config for both 4.4 and 4.19
09:35:08 <kazu> patersonc iwamatsu Thank you again
09:35:12 <iwamatsu> And I send PR to config repo, OK?
09:36:11 <masashi910> AI: add config for qemux86-64 and BBB. Is it reasonable?
09:36:22 <kazu> I'm OK, thanks
09:36:37 <masashi910> kazu: thanks.
09:36:45 <masashi910> any other business?
09:36:54 <masashi910> 3
09:36:59 <masashi910> 2
09:37:02 <masashi910> 1
09:37:03 <masashi910> #endmeeting