IRC logs for #cip for Thursday, 2019-06-06

*** OutBackDingo has quit IRC00:27
*** OutBackDingo has joined #cip00:29
*** helmut has quit IRC05:20
*** rajm has joined #cip06:57
*** Yamamodo has joined #cip08:51
*** vidda has joined #cip08:55
*** pave1 has joined #cip08:55
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Jun  6 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
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
szlin#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
szlinplease say hi if you're here09:00
pave1hi!09:00
viddahi09:00
Yamamodohi09:00
iwamatsuhi!09:00
patersonchi09:00
szlin#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
fujita[m]hi09:00
szlin1. send investigating email for kernel-testing lab to cip-dev - patersonc09:00
patersoncStill not done. Sorry09:01
szlinpatersonc: got it, I will keep this AI.09:01
szlin#topic Kernel maintenance updates09:01
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:01
*** sangorrin has joined #cip09:02
bwhhi09:02
sangorrinhi09:02
szliniwamatsu: pave1 Do you have any update on the topic of kernel maintenance updates09:02
pave1szlin: I reviewed v4.19.48 and am finishing v4.19.47 (that was over 200 patches).09:03
szlinpave1: wow, thank you!09:03
iwamatsuszlin; I  reviewd 4.4.158 and 159, and I send some patches for 4.4.y to stable@kernel.org09:03
szliniwamatsu: thank you!09:04
szlinso we can have new release in next Tuesday09:04
szlinbwh: Do you have any update on this topic?09:05
bwhno09:05
szlinbwh: thanks.09:05
szlinany other topic?09:05
pave1Actually yes.09:05
pave1I'm wondering if we could skip reviewing some of the stable patches.09:06
pave1For example, there are staging drivers and s390 architecture in the stable.09:06
bwhOf course you should skip those09:06
pave1So my proposal would be to create a list of "we are not reviewing this"09:06
pave1and then just mark it as "not reviewed -- out of scope" in the review list.09:07
szlinpave1: it's the topic of CIP kernel maintenance scope09:07
pave1I guess I could come up with list of paths we ignore and present it on the list.09:07
iwamatsupava1: That is a good idea.09:08
szlinpave1: awesome09:08
szlinbwh: do you have any comments on this?09:08
bwhIdeally we can use the collected configs to create a list of source files that members actually use09:09
pave1bwh: That might be even better, but I don't know how to do that.09:09
bwhHowever we don't have that for 4.19 yet09:10
pave1bwh: Plus it may limit future configurations.09:10
sangorrindo we need a script here?09:11
bwhI did find that someone did this before. I think it was using the "checker" hook in Kbuild to log each source file used.09:12
pave1If someone has a pointers to existing scripts, that would be very useful.09:13
bwhSo, I can have try to find that again, or reimplement it along those lines09:13
szlin#info https://elinux.org/images/3/39/Managing-Linux-Kernel-Configurations-with-Config-Fragments-Darren-Hart-VMware.pdf09:14
szlinbwh: so you will provide the script for CIP kernel config collection09:16
bwhOK09:16
szlinbwh: thanks :D09:16
iwamatsubwh: thanks.09:16
szlin#action Provide the script for CIP kernel config collection - bwh09:16
szlinany other topic?09:17
fujita[m]Does anyone kno09:17
fujita[m]sorry09:17
szlinfujita[m]: please go ahead09:17
fujita[m]Is there any plan about next cip-rt kernel release?09:17
szlinfujita[m]: ugh, we're discussing this topic today09:18
szlin#action Provide the plan about next cip-rt kernel release - szlin09:19
fujita[m]szlin: thank you09:20
szlinfujita[m]: any time09:20
szlinany other topic?09:20
sangorrinOne more thing, the configs for 4.19 probably need to be reviewed before we can say that everything in them needs to be supported. For example, some of them use CONFIG_NFS_FS which I think is hard to maintain.09:20
bwhYes. I am waiting to review those until all members have sent them09:21
sangorrinbwh: OK, thanks.09:21
szlin309:21
szlin209:21
szlin109:21
szlin#topic Kernel testing09:21
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:21
szlinpatersonc: give the floor to you :)09:22
patersoncThanks09:22
patersoncI've had meetings with Mentor about setting up a new LAVA lab for CIP.09:22
patersoncThey are currently waiting to exchange keys with the LF for the LAVA master.09:22
patersoncThey plan to add the SIMATIC IPC227E and Cyclone V DE0-Nano-SoC platforms.09:22
patersoncWe've also met and decided that CIP should use the gitlab-cloud-ci tool.09:22
patersoncMichael is going to submit a formal proposal to the TSC.09:22
patersoncDaniel is working on adding CI support for CIP Core (Deby).09:23
patersoncMichael has already added the same for ISAR.09:23
patersoncI need to sort out the Kernel builds...09:23
patersoncThat's it from me, unless there are any questions?09:23
szlinany comments?09:24
szlin309:24
szlin209:24
szlin109:24
szlin#topic CIP Core09:24
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:24
szlinThe below information were provided by Kazu09:25
szlin* Create patches so that isar-cip-core supports RZ/G1M iwg20m boards (on going)09:25
szlin* Create the "Debian 10 buster" based demonstration layers in deby, that supports QEMU x86 64bit and BeagleBone Black09:25
szlin* Held the first CIP-Core WG meeting and share the basic maintenance policies. Also planning to hold the second meeting to make a decision (or define action items) about the decision process of CIP maintained package list.09:25
*** _mungaip has joined #cip09:25
szlinany comments?09:25
szlin309:25
szlin209:25
szlin109:25
szlin#topic Software update09:25
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:25
szlinsangorrin: give you the floor09:26
sangorrinI am working on BBB watchdogs support now09:26
sangorrinrecentely a new command wdt was introduced, i want to add support for that on BBB as well09:26
sangorrinChristian is also working on the integration of swupdate in ISAR, it will take a week or two09:26
sangorrinthanks09:26
szlinsangorrin: thanks09:27
szlinany comments?09:27
szlin#topic AOB09:27
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:27
*** _mungaip has left #cip09:27
sangorrinfor those who are coming to OSSJ09:27
sangorrinif you come one day before (monday) we may have a meeting09:27
sangorrin1 day before the CIP meeting09:28
szlinsangorrin: do you mean swupdate meeting09:28
sangorrincip core, swupdate, testing, kernel..09:28
patersoncI wonder if we could meet during the conference at all?09:28
szlinsangorrin: ah, you mean f2f meeting09:29
sangorrinduring the conference, sure09:29
patersoncI think I'm likely to have internal meetings on Monday09:29
patersoncOr do we meet when the board meeting meets?09:29
sangorrinJan will come 1 day before09:29
sangorrinso we are going to have a meeting09:29
sangorrinbut of course we will have more meetings09:30
patersoncOkay09:30
sangorrinthanks09:30
szlinI would like to introduce my colleague09:31
szlinYamamodo: <- please welcome him09:31
szlin:D09:31
*** hungtran has joined #cip09:31
Yamamodohi, i am sz's partner, Moxa09:31
Yamamodonice to meet you09:31
pave1Hi, Yamamodo; nice to meet you!09:32
patersoncYamamodo: Hello!09:32
sangorrinhi Yamamodo, nice name09:32
sangorrinin Japanese: "mountain mode!"09:32
Yamamodohaha 3Q :)09:32
szlinany other business?09:32
iwamatsuYamamodo: Hi!09:33
szlin309:33
szlin209:33
szlin109:33
szlin#endmeeting09:33
brloggerMeeting ended Thu Jun  6 09:33:10 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:33
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-06-09.00.html09:33
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-06-09.00.txt09:33
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/06/cip.2019-06-06-09.00.log.html09:33
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:33
szlinthank you all09:33
sangorrinthanks!09:33
pave1Thank you!09:33
Yamamodo<sangorrin> in Japanese: "mountain mode!" => YES09:33
iwamatsuthank you09:33
fujita[m]thank you! and hello Yamamodo!09:33
*** sangorrin has quit IRC09:34
*** hungtran has quit IRC09:34
*** vidda has quit IRC09:35
*** Yamamodo has left #cip09:36
pave1Can we add new state to the review, for example09:36
pave1IGN: Patch was not reviewed as it is out of scope for CIP project09:36
pave1?09:36
iwamatsupave1; I think that is good.09:37
szlinpave1: +109:37
pave1Ok, will do :-).09:37
szlinpave1: BTW, do you have any question on CIP kernel release tutorial?09:38
pave1szlin: I did not get too close look, but it looks good so far.09:39
szlinpave1: thanks!09:39
*** Johnson has joined #cip09:39
pave1szlin: I guess more questions will arise when I try to follow it for the first time :-).09:40
*** Johnson has quit IRC10:06
*** pave1 has quit IRC10:10
*** CTtpollard has quit IRC13:12
*** tpollard has joined #cip13:15
*** helmut has joined #cip13:55
*** iwamatsu has left #cip22:08
*** rajm has quit IRC22:15

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!