IRC logs for #cip for Thursday, 2021-01-21

*** cp- has quit IRC02:33
*** cp- has joined #cip02:38
*** cp- has quit IRC02:43
*** cp- has joined #cip02:45
*** rajm has joined #cip06:53
*** samwilson has joined #cip06:56
*** samwilson has quit IRC08:08
*** samwilson has joined #cip08:08
*** fujita has joined #cip08:38
*** masashi910 has joined #cip08:39
*** pav31 has joined #cip08:58
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Jan 21 09:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brlogger`The 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
pav31hi09:00
iwamatsuhi09:00
wenshi09:00
masashi910Today, Yoshida-san is not here.09:00
masashi910#topic AI review09:01
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
masashi9101. Combine root filesystem with kselftest binary - iwamatsu09:01
masashi910iwamatsu: any update?09:01
iwamatsuNo update09:01
masashi910iwamatsu: Sure, thanks.09:01
masashi9102. Do some experiment to lower burdens on CI - patersonc09:01
masashi910patersonc: are you around?09:01
patersoncHi09:02
patersoncNo updates09:02
masashi910patersonc: Noted. Thanks.09:02
masashi9103. Check hitachi_omap defconfigs wrt CVE-2020-27820 [drm/nouveau UAF] - Hitachi-team09:02
masashi910We are waiting for the notification from Hitachi-team09:02
masashi910so, let's move on.09:02
masashi9104. Decide the timing to branch 5.10 to start CIP development - Kernel Team09:03
masashi910Pavel-san sent out the following email to cip-dev.09:03
masashi910https://lore.kernel.org/cip-dev/20210120192433.GA24348@duo.ucw.cz/1.1-a.txt09:03
masashi910Are any more works needed?09:03
pav31I think this one can be closed.09:03
pav31linux-5.10.y-cip tree was created, based on 5.10.8.09:03
masashi910pav31: Sure! Thanks very much! I will close this AI.09:04
iwamatsuthanks for your work.09:04
pav31Thank you :-)09:04
masashi910BTW, per discussion at the TSC call, I will send out some email asking CIP members to consider reference boards for 5.10.09:05
masashi910any other topics?09:05
patersoncAnd configs?09:05
masashi910patersonc: That's right! Thanks!09:05
masashi910309:06
masashi910209:06
masashi910109:06
masashi910#topic Kernel maintenance updates09:06
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:06
wensOne new issue this week regarding nfs4 kernel server. Fix is in Linus's tree but awaiting stable queue.09:06
iwamatsuI reviewed v4.4.25209:07
wensI also added 5.10-cip to the cip-kernel-sec tracker.09:07
pav31Lots of patch reviews: 5.10.8, 5.10.9 and corresponding 4.19/4.4 releases.09:07
masashi910wens, iwamatsu, wens: Thanks for your works!09:07
masashi910wens: Shall I make an AI to track that patch?09:08
wensit was cc-ed to stable, I think we don't need to track it.09:08
masashi910wens: Sure.09:08
wensbtw, Gitlab merge request issues still persist. SZ seemed to imply he would contact Gitlab admins.09:09
masashi910pave31: Thanks for your reviews. Do you think adding 5.10 for review targets works well?09:10
pav31masashi910: Keeping up with development had become more difficult, but I believe it will work out.09:11
masashi910pav31: Thanks!09:12
patersoncwens: it's strange that merge issue only happens on 1 project09:12
wenspushing works fine, so I doubt we hit some quota09:13
masashi910wens: At the IRC meeting last week, you mentioned some enhancement done on cip-kernel-sec by incorporating some contribution. Are there any co-relation between the contribution and the merge request issue?09:14
wensyes, the contribution is the one with the merge request issue.09:15
wenswhich is unfortunate as this makes reviewing harder09:15
patersoncwens: What repo is it again?09:16
patersoncAh cip-kernel-sec, sorry09:16
masashi910wens: You mean the contribution tried to fix the merge request issue or is it triggering the issue?09:17
wensmasashi910: the contribution is triggering the issue09:17
masashi910wens: I see...09:17
masashi910so, shall we wait for the result of SZ-san's action?09:18
wensSure. I will follow up with him as well.09:19
masashi910wens: Thanks! BTW, for the record, let me just log the url of your cip-kernel-sec report sent to cip-dev, as usual.09:19
masashi910https://lore.kernel.org/cip-dev/CAGb2v66bGEX3sCBNnYdv07cuojOjNe1Gf-D3Mb4Kik-He3nt0w@mail.gmail.com/1-a.txt09:19
masashi910any other topics?09:19
masashi910309:19
masashi910209:19
masashi910109:19
masashi910#topic Kernel testing09:19
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:20
masashi910patersonc: the floor is yours.09:20
patersoncI don't think I have much to add since the TSC on Tuesday.09:20
patersoncI'll add a pipeline for the 5.10 CIP testing later today09:21
pav31Thank you :-).09:21
masashi910patersonc: Thanks for your works!09:21
masashi910any other topics?09:22
masashi910309:22
masashi910209:22
masashi910109:22
masashi910#topic CIP Security09:22
*** brlogger` changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)"09:22
masashi910== Quote from yoshidak[m] ==09:22
masashi910There is no major update from Security working group.09:22
masashi910One thing, we plan to issue tickets about action lists to meet the certification09:22
masashi910requirements for development process on gitlab soon. Let's discuss to handle09:23
masashi910those requirements.09:23
masashi910====09:23
masashi910any other topics?09:23
masashi910309:23
masashi910209:23
masashi910109:23
masashi910#topic AOB09:23
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:23
masashi910Are there any business to discuss?09:23
masashi910309:24
masashi910209:24
masashi910109:24
masashi910There seem to be no topics to be discussed, so let's close the meeting.09:24
masashi910#endmeeting09:24
brlogger`Meeting ended Thu Jan 21 09:24:27 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:24
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-21-09.00.html09:24
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-21-09.00.txt09:24
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2021/01/cip.2021-01-21-09.00.log.html09:24
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:24
masashi910Thank you, and stay safe!09:24
iwamatsuthank you!09:24
pav31Thank you!09:24
wensThank you!09:31
*** pav31 has quit IRC09:36
*** rajm has quit IRC09:36
*** rajm has joined #cip09:37
*** fujita has quit IRC10:05
wensI posted a request on Gitlab's forum: https://forum.gitlab.com/t/500-error-when-creating-merge-requests/47830?u=wens10:16
*** tpollard has joined #cip12:04
*** samwilson has quit IRC12:06
*** samwilson has joined #cip12:07
patersoncHi iwamatsu: I see you're already working on 5.10-cip CI support?12:18
patersonchttps://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/tree/iwamatsu/linux-5.10.y-cip12:18
*** monstr has joined #cip13:17
masashi910wens: Thanks for posting the request!13:26
*** masashi910 has quit IRC13:27
*** patersonc has quit IRC15:19
*** patersonc has joined #cip15:30
*** samwilson has quit IRC16:52
*** cp- has quit IRC17:59
*** cp- has joined #cip18:08
*** cp- has quit IRC18:14
*** cp- has joined #cip18:30
*** toscalix has joined #cip18:34
*** samwilson has joined #cip19:20
*** tpollard has quit IRC20:19
*** samwilson has quit IRC21:01
*** toscalix has quit IRC22:49
*** rajm has quit IRC23:01
iwamatsupatersonc: thanks, I will check your comment.23:09

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