06:05:27 * ** patersonc has joined #cip
07:04:59 * ** rajm has joined #cip
07:34:35 * ** rajm has quit IRC
07:39:14 * ** toscalix has joined #cip
07:49:18 * ** rajm has joined #cip
07:59:52 * ** Tzongyen_Lin has joined #cip
08:00:11 * ** rajm has quit IRC
08:00:13 * ** hungtran has joined #cip
08:00:14 * ** moxavictor has joined #cip
08:00:26 * ** rajm has joined #cip
08:00:42 * ** patersonc has quit IRC
08:00:55 <gavinlai> szlin has a meeting conflict today
08:01:10 <gavinlai> I will chair this meeting :)
08:01:27 <gavinlai> #startmeeting
08:01:34 * ** sangorrin has joined #cip
08:01:36 <gavinlai> #roll call
08:01:40 <bwh> hi
08:01:45 <rajm> hi
08:01:48 <sangorrin> hello~
08:02:06 <gavinlai> please say hi if you are here
08:02:12 <hungtran> hi
08:02:54 <gavinlai> #topic action item review
08:03:22 <gavinlai> action item: Agustin will ping Ben for the feedback of git group account in kernel.org
08:04:32 <gavinlai> bwh: any feedback of git group account in kernel.org?
08:05:27 <bwh> I haven't asked yet. Does iwamatsu have a kernel.org account? It would be pointless to  have a group if no-one else can be in it yet.
08:06:48 <sangorrin> Apparently he doesn't
08:06:56 <sangorrin> Daniel Wagner has one
08:07:43 <sangorrin> probably we will need to wait until the next maintainer(s) are approved
08:08:10 <sangorrin> Is there any advantage in having the account in kernel.org instead of gitlab?
08:08:15 <gavinlai> ok, let's move to next action item?
08:08:46 <bwh> sangorrin: Well, I think it would be easier to just have it on Gitlab.
08:08:59 <bwh> But some people seem to think it looks more official if it's on kernel.org as well.
08:09:23 <bwh> "it" =  the CIP kernel repository
08:09:46 <bwh> gavinlai: OK
08:09:56 <sangorrin> yeah, we should consult with the marketing team then ;)
08:10:07 <gavinlai> action item: discuss the testing infra. including maintainer/admin at TSC meeting
08:10:33 <toscalix> o/
08:10:43 <sangorrin> gavinlai: I asked Ryan for permissions to use LAVA and KernelCI
08:11:16 <sangorrin> he said he had to upgrade LAVA, and then he will be sending tokens and calling for password exchanges
08:12:15 <gavinlai> got it
08:12:20 <sangorrin> Anyway, it doesn't look like we can get admin permissions.. only enough to set our boards
08:13:48 <gavinlai> I see, thanks
08:14:07 <gavinlai> any other updates?
08:14:42 <gavinlai> #topic kernel maintenance updates
08:15:03 <gavinlai> moxa team is working on sending our dts to mainline kernel
08:15:12 <gavinlai> #link https://lkml.org/lkml/2018/8/30/1136
08:15:33 * ** hungtran has quit IRC
08:15:36 <gavinlai> the TI employee suggests us to use phy-handle instead of phy_id which is deprecated.
08:16:10 <gavinlai> However, phy-handle is buggy on stable kernel 4.4
08:16:17 <gavinlai> moxa team has sent patches to fix phy-handle problem
08:16:32 <gavinlai> waiting for the review
08:16:47 <sangorrin> Is it normal to submit one dts per board? I thought the dts would better be in the yocto meta layer or the openWrt kernel etc.
08:18:05 <sangorrin> Thanks for the phy-handle fixes
08:21:12 <sangorrin> are you there gavinlai?
08:21:24 <gavinlai> sangorrin: I have no idea right now
08:21:43 <gavinlai> maybe we can figure out is there any rule or guideline ofr this
08:21:54 <toscalix> The kernel released yesterday is the last one under Ben H. responsibility. We should focus some energy in the transfer to the following maintainer.
08:22:32 <sangorrin> Hopefully, Iwamatsu-san will be approved soon
08:23:06 <gavinlai> any action item for transfer?
08:23:09 <toscalix> ah, I see. I will raise the topic then in the next TSC meeting
08:23:25 <toscalix> gavinlai: repo permissions
08:23:34 * ** hungtran has joined #cip
08:23:41 <sangorrin> bwh: do you have some notes about the workflow you have been using until now?
08:23:47 <toscalix> and probably an announcment in the cip-dev ML
08:24:24 <toscalix> sangorrin: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
08:24:37 <sangorrin> I think we need a script that can take patches and decide whether we should apply them to the cip kernel or not
08:24:40 <gavinlai> #action toscalix will raise topic in TSC meeting for transfer maintainer
08:25:04 <sangorrin> Jan suggested using machine learning today, but other methods can be used as well
08:25:29 <bwh> sangorrin: Nothing beyond what I put in the wiki about "how to review". But I can write something about whatever areas need them.
08:26:27 <gavinlai> next topic?
08:27:06 <gavinlai> #topic kernel testing
08:27:21 <sangorrin> bwh: ok thanks. Maybe Iwamatsu san needs to get used to your scripts here https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec
08:27:40 <rajm> hi, I've just successfully tested cip28 on b@d - email is on its way
08:27:41 <rajm> 
08:28:36 <toscalix> tested=build+boot on BBB with kernelci (B@D), for those unfamiliar with rajm work
08:28:43 <rajm> the containerisation is progressing, I've run lava-docker with builds from the b@d VM - issues with tftp I think which I'm going to ask kevin about
08:29:33 <rajm> and a MR of mine for kernelci-docker has been accepted
08:29:58 <gavinlai> rajm: thanks
08:30:04 <sangorrin> toscalix: will codethink use the centralized LAVA server?
08:30:25 <rajm> I've replicated a networking issue that renesas were experiencing so I can look further on that
08:31:16 <toscalix> sangorrin: my intention is that but I cannot make any commitment at this point beyond moving B@D to containers. I would need an internal ok to dedicate effort
08:31:24 <toscalix> to keep working on testing
08:32:34 <gavinlai> any other point for kernel testing?
08:32:43 <rajm> not from me!
08:33:00 <gavinlai> #topic AOB
08:33:06 <gavinlai> any other point?
08:33:11 <sangorrin> toscalix: ok, maybe you can wait until Chris or me prepare a simple guide to setup a typical board such as the beaglebone. Then it will be a matter of following that guide and ask me questions if there is a problem.
08:33:32 <toscalix> sangorrin: thanks
08:34:38 <gavinlai> 3
08:34:44 <gavinlai> 2
08:34:49 <gavinlai> 1
08:34:55 <gavinlai> #endmeeting