IRC logs for #cip for Thursday, 2019-03-28

*** dl9pf has quit IRC06:14
*** dl9pf has joined #cip06:27
*** dl9pf has joined #cip06:27
*** rajm has joined #cip07:42
*** sangorrin has joined #cip09:00
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Mar 28 09:00:21 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
sangorrinhi!09:00
patersonchi09:00
fujita[m]hi09:00
szlin._./09:00
szlin#topic AI review09:01
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
iwamatsu_hi09:01
szlin1. Please send configuration file of kernel 4.19 to cip-dev before the end of March.09:01
szlin2. Daniel has to upload to the wiki the SW updates tool comparison document09:01
szlinsangorrin: ^ could you please update this?09:01
sangorrinyes09:01
mungaip[m]hi09:01
sangorrinsorry, I will try to do it in april09:02
szlin3. Add a link to the SW updates wiki page from the embedded world CIP release page09:03
*** vidda has joined #cip09:03
szlinsangorrin:  ^ could you please update this?09:03
sangorrinI think we can drop this one, because Mae didn't update it09:03
szlinis it necessary?09:04
sangorrinwell, it was during the press release.. that's why I uploaded the wiki in a hurry.. but well09:04
szlinif it's unnecessary, I'll drop this AI.09:04
sangorrinyes, drop it09:05
szlinnoted.09:05
szlin#topic Kernel maintenance updates09:05
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:05
szlinIwamatsu announced the 4.4.176-cip31 stable release09:05
szlin#info https://lists.cip-project.org/pipermail/cip-dev/2019-March/001962.html09:05
szliniwamatsu_: are you around?09:05
iwamatsu_Yes.09:05
szliniwamatsu_: I've question with below link09:06
szlinhttps://gitlab.com/cip-project/cip-kernel/lts-commit-list/blob/master/linux-kernel-v4.4.176-commit.list#L4609:06
szlinis it an issue?09:06
iwamatsu_I am checking this. There are no  problems. Thanks, Pavel.09:07
patersonco/09:07
sangorrinwow that review was quick09:07
iwamatsu_And I am moving from  git to gitlab's wiki. https://gitlab.com/cip-project/cip-kernel/lts-commit-list/wikis/Review-linux-4.4.y.09:08
szlinamazing task, isn't it09:08
szliniwamatsu_: okay, so you'll check the review result from Pavel09:08
iwamatsu_szlin: yes.09:09
szlin#action The review results from Pavel will be confirmed by Iwamatsu-san09:09
szliniwamatsu_: thanks09:09
szlinpatersonc: go ahead please09:09
patersoncI have a question about https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=v4.4.176-cip3109:09
patersoncThe date of the commit is 201809:09
szlinpatersonc: good catch09:10
patersonciwamatsu_?09:11
iwamatsu_hmm09:11
*** rajm has quit IRC09:12
sangorrinntp not working?09:12
iwamatsu_There may be a problem with my develop machine...09:12
iwamatsu_Sorry about that.It's just time to switch to a new PC.09:13
szliniwamatsu_: would you like to update the time with re-uploading?09:13
iwamatsu_yes,09:14
iwamatsu_I will fix this, and update ASAP.09:14
iwamatsu_I will fix this, and update.09:14
patersoncThanks09:14
iwamatsu_patersonc: thanks for your check.09:15
szlin#action Iwamatsu-san will re-upload the 4.4.176-cip3109:15
szlinany other topics?09:15
szlin309:15
szlin209:15
szlin109:15
patersoncI have another question, briefly discussed yesterday.09:15
szliniwamatsu_: Chris proposed that we can have patch format with CIP patch09:15
szlinI mean, in the patch topic09:16
patersoncAs we have multiple target branches/repos (4.4/4.19/cip-core), I think we should use identifiers in patch submissions09:16
patersonc[PATCH 4.4-y] etc.09:16
patersoncLike Biju has done in his latest series yesterday09:16
iwamatsu_Yes, I know. I am reviewing about these.09:16
szlinand toscalix suggests we can discuss this rule via cip-dev09:17
patersoncGood shout. And document on the wiki09:17
sangorrinmaybe we can use a compose letter and put a subject prefix there09:18
patersoncIt's easier if it's done in the patches, as patchwork doesn't track cover letters.09:18
szlinpatersonc: could you send this proposal to cip-dev?09:19
patersoncSure09:19
szlin#action The proposal of CIP identifiers in patch submissions will be sent to cip-dev by Chris09:19
szlinany other topics?09:19
patersoncOne more (sorry)09:20
patersoncMy other question is about how to handle Patchwork. Is someone taking responsibility for assigning patches to maintainers?09:20
patersoncs|assigning|delegating09:20
szlinpatersonc: I can take this task09:20
patersoncThanks09:21
patersoncI don't know if Pavel is on the system?09:21
sangorrinI think we would need something like redmine09:21
patersoncsangorrin: How so?09:22
szlin#action Ask for the permission in patchework - szlin09:22
iwamatsu_Pavel is not on patchwork.09:22
sangorrinoh it can be done in gitlab as well09:22
patersoncFor patch reviews etc., we have patchwork: https://patchwork.kernel.org/project/cip-dev/list/09:22
sangorrinbasically you assign an issue to someone in gitlab, and it's pending until the assignee closes it09:23
patersonc#info For patch reviews etc., we have patchwork: https://patchwork.kernel.org/project/cip-dev/list/09:23
sangorrinouch09:23
sangorrinso we need an account there, dont we?09:23
patersonc#info people can create an account on patchwork here: https://patchwork.kernel.org/register/09:24
sangorrinok cool09:24
patersoncAn account is only needed if patches are to be delegated (maintainers). Developers generally don't need an account to submit patches.09:24
patersoncPatches are picked up by Patchwork automatically when they are sent to the cip-dev mailing list.09:25
szlinany comments?09:25
sangorrinso SZLin will need a list of maintainer user names i guess09:25
szlinsangorrin: Indeed, I will track on it09:26
szlinany other topics?09:27
sangorrinand maybe how many patches each maintainer can review per month, what subsystems he is an expert on..09:27
szlinsangorrin: fair enough09:27
sangorrinno more topics szlin sorry09:27
szlin#topic Kernel testing09:27
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:27
patersoncWe've fixed the MAC address issues on the boards in lab-cip-renesas09:28
patersoncCurrently investigating a potential DHCP client issue in the CIP v4.4 Kernel09:28
patersoncAny questions/comments?09:28
sangorrinI added Jan to AWS09:29
sangorrinhe will prepare images for S309:29
sangorrinmaybe with kubernetes09:29
sangorrinI tried to create a debian rootfs for iwg20m09:30
sangorrini will upload it at sometime and test it09:30
patersoncGreat09:30
patersoncThank you09:30
szlinany topics?09:30
sangorrinit would be nice to have NBD in the long term09:30
sangorrinto run some LTP tests09:30
sangorrinno more topics from me09:31
szlin309:31
szlin209:31
szlin109:31
szlin#topic CIP Core09:31
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:31
sangorrindeby: we fixed a few issues (See github)09:32
szlinany other topics?09:32
sangorrinwe discussed about naming09:32
sangorrinbut we will talk about that in tSC09:33
sangorrindeby v2 etc09:33
sangorrinno more topics09:33
szlin#action Discuss the naming of deby in TSC - Daniel Sangorrin09:33
szlin309:34
szlin209:34
szlin109:34
szlin#topic Software update09:34
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:34
sangorrinSuzuki-san produced a working example09:34
szlinI've repackaged the swupdate since it released new version.09:34
sangorrinof a software update, thanks to Christian for the help09:34
sangorrinthanks09:34
szlinany other comments?09:35
szlin309:35
szlin209:35
szlin109:35
szlin#topic AOB09:35
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:35
szlinany other business?09:35
sangorrini will be in Thailand next week09:35
sangorrinfor the Linaro Connect09:35
sangorrinif anyone is going let me know09:36
szlinsangorrin: stay safe09:36
mungaip[m]sangorrin: quick question- I've never worked with NBD, is it hard to set up?09:36
sangorrinI haven't either, but it should be something like NFS09:36
szlin309:37
szlin209:37
szlin109:37
szlin#endmeeting09:37
brloggerMeeting ended Thu Mar 28 09:37:13 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:37
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/03/cip.2019-03-28-09.00.html09:37
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/03/cip.2019-03-28-09.00.txt09:37
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/03/cip.2019-03-28-09.00.log.html09:37
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:37
mungaip[m]Okay, thanks :)09:37
szlinthank you all09:37
iwamatsu_thank you09:37
mungaip[m]Thanks szlin09:37
patersoncThanks09:37
gavinlaithanks09:37
sangorrinThanks09:37
*** sangorrin has quit IRC09:54
*** vidda has quit IRC10:24
*** rajm has joined #cip11:36
*** rajm has quit IRC22:56

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