toggle quoted messageShow quoted text
Thanks for updating your status. Also thanks for following up the AI#2.
I will close this.
From: firstname.lastname@example.org <email@example.com> On Behalf Of
Sent: Thursday, November 19, 2020 12:20 PM
Subject: Re: [cip-dev] CIP IRC weekly meeting today
Sorry, I can not join today's IRC meeting.
-----Original Message-----technical topics with CIP kernel today.
[mailto:firstname.lastname@example.org] On Behalf Of
Sent: Thursday, November 19, 2020 9:20 AM
Subject: [cip-dev] CIP IRC weekly meeting today
Kindly be reminded to attend the weekly meeting through IRC to discuss
*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00
starting from the first week of Apr. according to TSC meeting*
USWest USEast UK DE TW JP
01:00 04:00 9:00 10:00 17:00 18:00
Last meeting minutes:
* Action item
1. Combine root filesystem with kselftest binary - iwamatsu
2. Check whether CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 needsAfter IRC meeting, I checked stable ML. Ben was sending a patch for this issue.
to be backported to 4.4 - Kernel Team
I checked the contents of the patch, but the contents were the same as the patch I
posted to this ML.
And these patches have been applied to stable tree, we can close this A.I.
* Kernel maintenance updatesI reviewed 4.4.244-rc1.
* Kernel testingwill be taken offline or in the next meeting.
* CIP Security
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
Cybertrust Japan Co., Ltd.