IRC logs for #cip for Thursday, 2020-04-16

*** rajm has joined #cip06:49
*** user_____ has joined #cip07:28
*** user_____ is now known as pavel207:29
*** masashi910 has joined #cip07:32
*** pavel1 has joined #cip07:52
pavel1Weekly meeting is starting in 50 minutes, right?08:11
*** tpollard has joined #cip08:38
*** fujita3 has joined #cip08:57
masashi910#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Apr 16 09:00:00 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at
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
masashi910#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
masashi910#topic AI review09:00
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
masashi9101. Combine root filesystem with kselftest binary - Iwamatsu-san09:00
iwamatsumasashi910: no update09:01
masashi910iwamatsu: Noted. Thanks.09:01
masashi9102. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team09:01
masashi910The current discussion among the kernel team is described in the following document.09:01
masashi910Since last week, I added some statistics.09:02
masashi910If you have any ideas, please write down to the document.09:02
masashi910so, let me move on.09:02
masashi9103. Upload a guideline for reference hardware platform addition - masashi91009:02
masashi910Regarding this one, updates can be reported around June timeframe.09:03
masashi910so, let me move on.09:03
masashi9104. Identify target boards and configs for RT kernel testing (4.4rt and 4.19rt) - masashi91009:03
masashi910I got responses from board owners and compiled the result to make a list.09:03
masashi910I will talk with Chris-san later, because he is not joining this call.09:03
masashi9105. Clarify the requirement about sytem-backup - Yoshida-san09:04
pavel1board configs...09:04
pavel1for realtime. I believe we can use existing09:04
pavel1non-rt configs for now.09:04
pavel1Eventually we'll get realtime testing to work and can switch.09:05
pavel1(that was for ai 4)09:05
masashi910pavel1: rt-config is requested by Renesas, Chris-san.09:05
pavel1I know. It makes sense to enb09:06
iwamatsuwe already have rt config in ci--kernel-config.09:06
pavel1enable when we get rt testing to work.09:06
masashi910pavel1: so you prefer to start with non-rt config on RZ/G[12]M as well?09:07
pavel1if rt config is available it is better to use it.09:08
pavel1but I dont see it as critical at the moment.09:08
masashi910pavel1: ok. according to Iwamatsu-san, rt-config is already there. so if there are any issues, let's discuss.09:09
masashi910pavel1: Thanks!09:09
iwamatsui see. I have a RZG1 for testing kernel. I will create rt-config for RZG109:09
masashi910iwamatsu: Thanks!09:10
masashi910Yoshida-san, are you around?09:10
iwamatsumasashi910: please add this to A.I.09:10
yoshidak[m]masashi910: yes09:11
masashi910iwamatsu: Sure! thanks again!09:11
masashi910yoshidak[m]: do you have update on AI-5: Clarify the requirement about sytem-backup09:12
yoshidak[m]I've updated the above docs.09:12
* yoshidak[m] sent a long message: < >09:13
yoshidak[m]I'll eventually update the requirement sheet that I've sent, but would it be easier to understand if the bullet points were used like this?09:13
yoshidak[m]the above docs means...09:14
masashi910yoshidak[m]: this document is dedicated for the self-maintenance disucssion.09:15
yoshidak[m]Oops, sorry.09:15
masashi910yoshidak[m]: so, please find a different document for this update.09:15
masashi910yoshidak[m]: anyway, thanks for your update.09:16
yoshidak[m]OK. I'll reply to the mail. Anyway, those 4 functional requirements are needed to the system backup.09:16
masashi910are there any queries?09:16
masashi910If there is no query on AI-5, I will close this AI.09:17
masashi910#topic Kernel maintenance updates09:18
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:18
pavel1I have reviewed 4.19.115 and released 4.4-rt.09:18
iwamatsuI reviewed 4.4.220-rc.09:19
pavel1I looked at 4.19-rt update, but suitable upstream -rt release was not available.09:19
wenslots of CVEs last week. some need backports:09:19
wensone for btrfs, one for f2fs, four for ext409:19
masashi910wens: thanks very much. I will take a look.09:21
masashi910pavel1, iwamatsu: thank you for your updates.09:22
wensAFAIK these were found with fuzzer09:22
masashi910any other topics?09:22
masashi910wens: fuzzer seems to be doing a very good job finding many issues.09:22
wensso probably not very critical, unless you have faulty hardware that does bitflips09:22
masashi910wens: yes, thanks for this info.09:23
wensmasashi910: yeah. I suppose code is mostly written with the assumption that hardware does not do funny things09:23
masashi910any other topics?09:24
wensbwh: thanks for reviewing btw09:24
masashi910#topic Kernel testing09:25
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:25
masashi910Quote from Chris-san "No major updates to report from the testing working group."09:25
masashi910any other topics?09:25
masashi910#topic CIP Core09:25
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:25
masashi910== Quote from punit ==09:25
masashi910Discussion around projected EOL for CIP core support on cip-dev. Based on the comments in the TSC I will update the proposal to YYYY-MM  format.09:26
masashi910Daniel to take over CIP Core activities going forward09:26
masashi910any other topics?09:26
masashi910#topic Software update09:26
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:26
masashi910Suzuki-san, the floor is yours09:26
masashi910Suzuki-san, are you around?09:27
masashi910So, let's move on.09:27
masashi910#topic CIP Security09:28
*** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:28
masashi910Yoshida-san, the floor is yours09:28
yoshidak[m]No major updates to report from the security working group in this week.09:28
iwamatsumasashi910: Suzuki-san has take a holiday09:28
masashi910iwamatsu: I see. Thanks.09:28
masashi910yoshidak[m]: Noted. Thanks.09:29
masashi910any other topics?09:29
masashi910#topic AOB09:29
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:29
masashi910Are there any business matters to discuss?09:30
brloggerMeeting ended Thu Apr 16 09:30:18 2020 UTC.  Information about MeetBot at . (v 0.1.4)09:30
brloggerMinutes (text):
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at"09:30
masashi910Thank you! Stay safe!09:30
pavel1Thank you!09:30
iwamatsuthank you!09:30
szlinthank you09:30
yoshidak[m]Thank you!09:31
wensthank you!09:31
fujita3Thank you!09:31
*** fujita3 has quit IRC09:35
*** pavel1 has quit IRC14:21
*** tpollard has quit IRC14:57
*** tpollard has joined #cip14:57
*** toscalix has joined #cip17:58
*** tpollard has quit IRC18:19
*** tpollard has joined #cip18:29
*** tpollard has quit IRC18:34
*** tpollard has joined #cip19:15
*** tpollard has quit IRC19:45
*** toscalix has quit IRC20:23
*** rajm has quit IRC22:16
*** kimmoli_ has joined #cip23:33
*** kimmoli has quit IRC23:34

Generated by 2.15.3 by Marius Gedminas - find it at!