cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Subject: Re: CIP IRC weekly meeting today
Date: Thu, 30 Apr 2020 07:53:11 +0000	[thread overview]
Message-ID: <OSAPR01MB3667B7F6BD8666E1A789657E92AA0@OSAPR01MB3667.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY2PR01MB497292B5ABFEA4BC5CC874F9A0AA0@TY2PR01MB4972.jpnprd01.prod.outlook.com>

Hi Kudo-san,

I am on vacation and cannot attend IRC meetings today.
And other Toshiba members (Daniel-san, Suzuki-san) are in the same situation.

> -----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, April 30, 2020 9:57 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=30&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-23-09.00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine root filesystem with kselftest binary - Iwamatsu-san

No update.

> 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
> 3. Upload a guideline for reference hardware platform addition - masashi910
> 
> * Kernel maintenance updates

I reviewd v4.4.219 and 220.

> * Kernel testing
> * CIP Core
> * Software update
> * CIP Security
> * AOB
> 1. Some topics from TSC call
> 
> 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,

Best regards,
  Nobuhiro


> --
> M. Kudo
> Cybertrust Japan Co., Ltd.

  reply	other threads:[~2020-04-30  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  0:56 CIP IRC weekly meeting today masashi.kudo
2020-04-30  7:53 ` Nobuhiro Iwamatsu [this message]
2020-04-30  7:59   ` [cip-dev] " masashi.kudo
2020-04-30  8:31     ` Akihiro Suzuki
2020-04-30  8:33       ` masashi.kudo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OSAPR01MB3667B7F6BD8666E1A789657E92AA0@OSAPR01MB3667.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).