Hi, Iwamatsu-san,

Thanks for your email.
I noticed that you put (CIP) after your name when you committed those backports.
Thanks!

Best regards,
--
M. Kudo

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Nobuhiro Iwamatsu
Sent: Thursday, May 21, 2020 3:08 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi,

Sorry, I can not join IRC meeting today.

> -----Original Message-----
> From: cip-dev@lists.cip-project.org 
> [mailto:cip-dev@lists.cip-project.org] On Behalf Of 
> masashi.kudo@cybertrust.co.jp
> Sent: Thursday, May 21, 2020 9:37 AM
> To: cip-dev@lists.cip-project.org
> Subject: [cip-dev] CIP IRC weekly meeting today
> 
> Hi all,
> 
> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 
> *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 
> starting from the first week of Apr. according to TSC meeting* 
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&m
> onth=5&day=21&hour=9&min=0&sec=0&p1=224&p2=
> 179&p3=136&p4=37&p5=241&p6=248
> 
> USWest	USEast	UK	DE	TW	JP
> 02:00	05:00	10:00	11:00	17:00	18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/05/cip.2020-05-14-09.00
> .log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine root filesystem with kselftest binary - iwamatsu

No update.

> 2. Strengthen sustainable process to backport patches from 
> Mainline/LTS - Kernel Team 3. Upload a guideline for reference 
> hardware platform addition - masashi910 4. Propose a reduction of 
> kernel repository mirrors to TSC  - masashi910, szlin 5. Post LTP 
> results to KernelCI - patersonc 6. Ask board owners to review 
> reference platform configs to optimize backporting - masashi910
> 
> 
> * Kernel maintenance updates

I reviewed v4,4.223 and 224.
And I sent a patch for fixing CVE-2020-12769 to 4.4, and 4.9 and 3.16.
This was alreadly applied to each LTS tree.

> * Kernel testing
> * CIP Core
> * Software update
> * CIP Security
> * AOB
> 
> The meeting will take 30 min, although it can be extended to an hour 
> if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

Best regards,
  Nobuhiro