Re: CIP IRC weekly meeting today


masashi.kudo@cybertrust.co.jp
 

Hi, Suzuki-san,

Thanks for sharing the status.

Best regards,
--
M. Kudo

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Akihiro Suzuki
Sent: Thursday, April 23, 2020 5:41 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi Kudo-san and all,

Sorry, I've got a plan already today. So I'll be absent from today's IRC meeting.
SW Updates WG don't have any progress this week.

Best regards,
Suzuki


-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of masashi.kudo@cybertrust.co.jp
Sent: Thursday, April 23, 2020 9:07 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&month=4&day=23&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/04/cip.2020-04-16-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team 2-1. Workflow for identifying important fixes, backporting, and reviewing them 2-2. Prepare the tools to be used for this workflow 2-3. Get practice in backporting patches 3. Upload a guideline for reference hardware platform addition - masashi910 4. Identify target boards and configs for RT kernel testing (4.4rt and 4.19rt) - masashi910

* Kernel maintenance updates
* 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,
--
M. Kudo
Cybertrust Japan Co., Ltd.

Join cip-dev@lists.cip-project.org to automatically receive all group messages.