00:14:18 * ** dl9pf has quit IRC
00:15:59 * ** dl9pf has joined #cip
00:16:00 * ** dl9pf has joined #cip
01:06:47 * ** alicef[m] has quit IRC
01:07:06 * ** alicef[m] has joined #cip
01:37:56 * ** alicef[m] has quit IRC
01:44:21 * ** alicef[m] has joined #cip
06:33:48 * ** patersonc has joined #cip
07:35:20 * ** rajm has joined #cip
07:54:51 * ** hungtran has joined #cip
07:55:45 * ** toscalix has joined #cip
07:57:32 * ** szlin_ is now known as szlin
08:00:07 <szlin> #startmeeting
08:00:16 <szlin> #roll call
08:00:23 <szlin> please say hi if you're around
08:00:26 <patersonc> hi
08:00:28 <iwamatsu_> hi
08:00:29 <hungtran> hi
08:00:31 <rajm> hi
08:00:34 <bwh> hi
08:01:01 <szlin> #topic AI review
08:01:04 <szlin> AI: patersonc will apply patchwork for CIP kernel maintenance team
08:01:13 <szlin> patersonc: do you have any updates on it?
08:01:27 * ** sangorrin has joined #cip
08:01:34 <patersonc> I've raised a ticket with Kernel.org to create a patchwork instance for us, no response so far
08:02:55 <szlin> patersonc: Does the ticket have public URL?
08:03:20 <patersonc> I don't think so, sorry
08:03:31 <szlin> patersonc: got it, thanks for the update
08:03:41 <patersonc> https://rt.linuxfoundation.org/SelfService/Display.html?id=61828 - but I think you need to login, and I assume only I can see it
08:04:06 <patersonc> I sent a reminder this morning (ticket was raised last Friday)
08:04:41 <szlin> patersonc: I see, let's wait for few days.
08:05:02 <szlin> #topic kernel maintenance updates
08:06:00 <szlin> I don't have any update since I'm having my personal leave this week.
08:06:23 <szlin> any other points?
08:06:30 <sangorrin> Hi SZ
08:06:41 <szlin> sangorrin: (wave
08:06:56 <sangorrin> I was wondering if we should create wiki page with Ben's advice about kernel configuration
08:06:57 * ** mungaip has joined #cip
08:07:07 <sangorrin> Mail 1: https://lists.cip-project.org/pipermail/cip-dev/2017-May/000263.html
08:07:10 <sangorrin> Mail 2: https://lists.cip-project.org/pipermail/cip-dev/2017-July/000387.html (TODO)
08:07:15 <sangorrin> Mail 3: https://lists.cip-project.org/pipermail/cip-dev/2018-October/001578.html
08:07:34 <sangorrin> I think that information is valuable
08:08:07 <bwh> It's probably worth linking to those mails
08:08:21 <bwh> Not all of that will be applicable to the next CIP kernel branch
08:08:50 <sangorrin> Maybe we can maintain advice for each kernel branch
08:09:43 <szlin> sangorrin: I agree with that, it's very important to collect the valuable information together.
08:10:20 <sangorrin> OK, then I will prepare something
08:10:35 <patersonc> o/
08:11:44 <szlin> patersonc: please
08:11:48 <patersonc> Is anyone able to review/merge this patch? iwamatsu_? https://lists.cip-project.org/pipermail/cip-dev/2018-September/001552.html
08:13:02 <iwamatsu_> patersonc: OK, I will check this patch tomorrow.
08:13:22 <szlin> #agreed create a wiki page for CIP kernel configuration
08:13:23 <patersonc> Thank you. It's nothing major, I just don't want to forget about it :)
08:13:40 <szlin> sangorrin: would you be the owner for creating the wiki page?
08:14:17 <iwamatsu_> patersonc: :-)
08:14:34 <szlin> #action iwamatsu will review the CIP patch - https://lists.cip-project.org/pipermail/cip-dev/2018-September/001552.html
08:14:42 <sangorrin> patersonc: what in the patch changes "voltage tolerance"?
08:14:47 <szlin> iwamatsu_: thank you!
08:15:38 <sangorrin> szlin: yes, I think I can do that
08:16:35 <szlin> #action sangorrin will create wiki pages for CIP kernel configuration
08:16:41 <szlin> sangorrin: thank you!
08:17:21 <patersonc> sangorrin: Good question. The commit message comes from the upstream patch. The corresponding property "voltage-tolerance" was dropped from the backport, I'm guessing because v4.4 doesn't support it.
08:18:30 <szlin> any other points?
08:18:36 <sangorrin> patersonc: I think there needs to be a reference to the upstream commit in the commit log of the backported patch
08:18:55 <patersonc> sangorrin: There is: (cherry picked from commit 8199e49ff1f654bbe8bed90fd6710bc097a89d02)
08:20:04 <szlin> it should be "commit #hash upstream"
08:20:37 <szlin> and put that in the first line, if I recalled correctly.
08:20:49 <bwh> I've accepted either
08:21:05 <patersonc> I guess it's up to the maintainers - I believe this is the style we've used with all our backports :)
08:21:13 <bwh> "commit <hash> upstream." is what's recommended in stable_kernel_rules
08:21:18 <szlin> https://www.kernel.org/doc/Documentation/process/stable-kernel-rules.rst
08:21:22 <bwh> whereas the other is actually supported by git itself
08:21:58 <bwh> In practice you'll find both in stable branches
08:22:05 <patersonc> szlin: Thank you for the link. I'll take a look.
08:22:48 <szlin> bwh: if I recalled correct, I had seen some backport patches were rejected by that reason.
08:22:59 <szlin> s/correct/correctly
08:23:02 <sangorrin> patersonc: Ok, I saw the upstream patch now and I see that other dts files had the "voltage-tolerance" keys.
08:23:55 <szlin> any other points?
08:23:56 <patersonc> sangorrin: Yes. We'll try and add a clearer description next time around. It gets tricky because we aren't trying to backport for all platforms, just the CIP ones.
08:24:56 <szlin> 3
08:24:59 <szlin> 2
08:25:00 <szlin> 1
08:25:03 <szlin> #topic kernel testing
08:25:10 <rajm> hi, regular health checks running on both the BBB and iwg20m
08:25:19 <rajm> b@d provisioned box from latest repos prepared - hopefully it'll be uploaded tomorrow (so it has the iwg20m changes in it)
08:25:30 <rajm> (I've been busy preparing an internal intro to LAVA session)
08:25:40 * rajm ends update
08:26:03 <szlin> rajm: thank you for the updates
08:26:32 <szlin> any points?
08:26:54 <szlin> 3
08:26:55 <szlin> 2
08:27:00 <szlin> 1
08:27:02 <szlin> #topic AOB
08:27:36 <szlin> any other business?
08:27:56 <szlin> 3
08:28:05 <szlin> 2
08:28:06 <szlin> 1
08:28:09 <szlin> #endmeeting