IRC logs for #cip for Thursday, 2019-09-26

« Wednesday, 2019-09-25 Index Friday, 2019-09-27 »
*** wens has joined #cip05:09
*** rajm has joined #cip06:01
*** therisen has joined #cip07:46
szlinwens: (wave08:47
wensszlin: (wave08:50
*** pave1 has joined #cip08:57
*** masashi910 has joined #cip08:59
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Sep 26 09:00:01 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 are around09:00
pave1hi09:00
patersonchi09:00
fujita[m]hi09:00
szlin#topic AI review09:01
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
szlin1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san09:01
szliniwamatsu: are you around?09:01
masashi910hi09:01
szlinI will keep this AI.09:01
szlin2. Test LTS (pre)releases directly - patersonc09:01
patersoncI've sent an email to cip-dev with details of what i've done so far09:02
*** kazu has joined #cip09:02
szlinpatersonc: thank you.09:02
patersoncEssentially: https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines09:02
szlin#info https://gitlab.com/cip-playground/linux-stable-rc-ci/pipelines09:02
szlin#topic Kernel maintenance updates09:02
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:02
wenshi09:03
szlinI've started working on cip-kernel-sec, and the MR has been sent.09:03
szlinpave1: do you have any update on kernel maintenance?09:03
pave1I have reviewed 4.19.75 and 4.19.35.09:04
pave1Also 4.4-rt kernel should now build.09:04
szlinpave1: thank you for your work09:05
szlinpave1: I am curious why you review 4.19.35 this time09:06
szlinfor rt or something else?09:06
pave1Well, I thought that we'll eventually want whole 4.19.X reviewed, so I started going down from patches we have already reviewed.09:07
szlinpave1: I see, thanks :)09:07
szlinany other topics?09:07
szlin309:07
szlin209:07
szlin109:07
szlin#topic Kernel testing09:07
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:07
szlin#info https://lists.cip-project.org/pipermail/cip-dev/2019-September/003334.html09:08
szlin^ any feedback is welcome09:09
szlinpatersonc: do you have any update on kernel testing?09:09
pave1This looks very good, I'll take a detailed look.09:09
patersoncThanks pave109:10
patersonc#info CI Kernel jobs now store the Kernel config, even if the build fails.09:10
szlinpave1: thank you.09:10
patersonc#info lab-cip-mentor will move over to new hardware today, so there may be some downtime.09:10
patersonc#info Initial prototype created to automatically build and test the stable-rc releases.09:10
patersonc#link https://lists.cip-project.org/pipermail/cip-dev/2019-September/003334.html09:10
patersoncThat's it from me, unless there are any comments/queries?09:10
szlinpatersonc: I'm thinking to add some test slide in ELCE session, let's discuss this offline09:11
patersoncszlin: Great09:11
szlinany other topics?09:11
szlin309:11
szlin209:11
szlin109:11
szlin#topic CIP Core09:11
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:11
kazuThe project porposal (cip-pkglist) is accepted in TSC.09:11
kazuThank you for your voting!09:12
kazuI will move the repo to cip-project/cip-core soon.09:12
kazuPDP updated: Use the following script to get the number of CVEs in a Debian package09:12
kazuhttps://gitlab.com/cip-playground/cip-pkglist/blob/master/count_cve.py09:12
szlinkazu: Congradulations, and thank you for your effort!09:12
kazuI will formally inform this in cip-members soon. After reviewed, start the review process for CIP security WG packages ASAP09:13
patersonckazu: Don't all member companies get a vote in TSC?09:13
kazuszlin Thank you09:13
patersoncYou said in your email that only the platinum members get a vote09:13
kazuI got votes from all member companies,09:14
kazuI'm not sure if I should ask only voting from platinum members09:14
patersoncAh sorry, it was Yoshi-san's email09:15
patersoncIgnore me :)09:15
szlinany other topics?09:15
kazunothing from me09:15
szlin#action Move cip-core repo to cip-project/cip-core - kazu09:15
szlin309:15
szlin209:16
szlin109:16
szlin#topic Software update09:16
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:16
kazuI don't get any updates from Suzuki-san at the moment09:16
szlinkazu: thanks.09:16
szlinany other topics?09:16
szlin309:16
kazuHe are focusing on creating demo09:16
szlin209:16
szlinkazu: does he need any assistence?09:17
kazuI will ask him then let members know if needed :-)09:17
szlinkazu: thanks09:17
szlin109:17
szlin#topic AOB09:17
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:17
szlinLet's welcome wens - new kernel team member09:18
szlinwens: \o/09:18
* wens waves09:18
pave1Welcome :-).09:18
kazuwelcome!09:18
patersoncHello wens09:18
wensthanks everyone :)09:18
laurence-hi wens !09:18
masashi910Hello, Wens!09:19
szlinwens is an active kernel maintainer09:19
wensmy kernel experience up to now mostly involves the Allwinner platform, with odd bits here and there09:19
szlinwens: thank you for your introduction09:20
szlinany other topics?09:20
szlinis kudo-san here?09:21
patersoncszlin: Have you had many responses for the kernel meeting at ELC-E?09:21
masashi910Yes, I'm here.09:21
szlinpatersonc: so far I got 3 responses.09:21
masashi910Can I propose some contribution activity?09:21
szlinCIP kernel & Testing WG would like to have a f2f discussion during ELCE 2019, please reply your available time via "doodle" link.09:22
pave1I'm have a talk at OSS 2019, and I'm not sure what the time will be at the moment.09:22
pave1So I can vote but if there's collision I'll have to be at my talk.09:23
szlinpave1: feel free to choose your prefer timeslot09:23
fujita[m]Can we connect via zoom meeting?09:23
szlinfujita[m]: IIRC, OSS & ELCE are in the same venue09:23
szlinfujita[m]: and yes, zoom will be setup then09:24
fujita[m]Good. Thank you.09:25
szlinOnce the time is confirmed09:25
szlinmasashi910: sorry for the delay, the floor is yours09:25
masashi910Thanks, SZ-san.09:25
patersoncpave1: This one? https://sched.co/TPHT09:26
masashi910Now I would like to propose MPSoC code contribution to CIP tree.09:26
pave1patersonc: Aha, yes, that one. Thanks a lot!09:26
fujita[m]masashi910: Do you have a plan to propose another reference board using MPSoC?09:28
masashi910Cybertrust would like to contribute the MPSoC code to CIP tree. The detail is described in the PDF I sent earlier.09:28
masashi910I would like to get approval from the team to move it forward.09:28
masashi910Does anyone have any comments or questions?09:29
pave1masashi910: If you have pointer to the PDF, that would be useful.09:29
szlinmasashi910: so that means Cybertrust will take the backport task, kernel team need to take maintenance task.09:30
masashi910Pavel: Sorry I don't know how to share the document in this IRC channel. Shall I resend the pdf to you?09:31
szlinpave1: http://lists.cip-project.org/pipermail/cip-dev/attachments/20190926/19df8723/attachment-0001.pdf09:31
szlinmasashi910: ^ I think it's this one09:31
pave1szlin: Thank you.09:31
szlinmasashi910: IMHO, we need more time to look on it09:32
masashi910szlin: Thanks.09:32
szlin#action Review the proposal from Kudo-san - Kernel team09:33
masashi910zlin: Sure, then shall I come back next week as well?09:33
szlinmasashi910: is that ok for you?09:33
masashi910szlin: Yes. Thanks.09:33
szlinmasashi910: yes, perhaps we can reply it beforehand09:33
szlinmasashi910: thanks09:33
szlinany other topics?09:34
szlin309:34
szlin209:34
szlin109:34
szlin#endmeeting09:34
brloggerMeeting ended Thu Sep 26 09:34:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:34
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-26-09.00.html09:34
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-26-09.00.txt09:34
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-26-09.00.log.html09:34
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:34
szlinthank you all09:34
kazuThank you09:34
szlinmasashi910: not sure if you saw my question - so that means Cybertrust will take the backport task, kernel team need to take maintenance task09:34
masashi910Thanks09:35
pave1Thank you!09:35
szlinor Cybertrust will maintain these codes as well09:35
masashi910szlin: Cyberturst will backport and maintain the MPSoC code. This is our current plan.09:36
pave1For the record, I don't see a problem with new platform.09:36
masashi910pavel: Thanks for your comment.09:36
pave1If there's draft version of patch to look at, that would be useful.09:37
pave1(Or pointer which drivers from mainline will need to be backported or something like that.)09:37
fujita[m]masashi910: Are you assuming to add drivers? or need some changes inside the kernel?09:38
masashi910pavel: We are not ready for that. If this activity is approved, we will prepare the code for review.09:38
pave1Is the support for Xilinx MPSoC upstream at the moment?09:38
masashi910pavel: Yes.09:39
szlinmasashi910: I see, thanks. I'm thinking about maybe we need to create a standard process for this activiy09:39
masashi910fujita[m]: Mostly drivers, I assume.09:40
pave1masashi910: What dts would that be? I tried quick grep but could not find it.09:40
masashi910pavel: Currently, we picked up 400 patches from MPSoC BSP, and applied to CIP SLTS 4.19 locally in order to experiment whether it works or not.09:41
masashi910pavel: At this moment, we successfully have done that. As a next step, we need to examine whcih patches are in the Mainline already. After that we will propose patch bundles to apply CIP tree.09:43
pave1masashi910: We don't need working version at the moment. But if you could mail the patches, or post pointer for them, or at least diffstat... That would help.09:43
masashi910pavel: Thanks. Our work is currently being done locally. I will discuss our team how to share the patches with you.09:44
patersoncmasashi910: Are you planning to set up your own LAVA worker?09:45
pave1masashi910: Ok. Are you targetting 4.4-cip or 4.19-cip?09:45
pave1masashi910: Or both?09:45
masashi910patersonc: Let me check. I will get back to you by email.09:45
masashi910pavel: Only 4.19-cip.09:46
pave1masashi910: Ok, that probably makes sense, thanks.09:46
masashi910pavel: Thanks.09:47
*** kazu has quit IRC09:48
*** masashi910 has quit IRC10:39
*** pave1 has quit IRC10:53
*** masashi910 has joined #cip11:57
patersonctherisen: Hello?12:25
therisenyes12:29
theriseni've sent you a direct message12:30
therisenah12:30
theriseni /query patersonc12:30
*** rajm has quit IRC12:51
*** masashi910 has quit IRC13:17
*** masashi910 has joined #cip14:19
*** masashi910 has quit IRC14:27
*** therisen has quit IRC14:59
*** masashi910 has joined #cip22:09
*** masashi910 has quit IRC22:15
« Wednesday, 2019-09-25 Index Friday, 2019-09-27 »

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