CIP-dev Archive on lore.kernel.org
 help / color / Atom feed
* [cip-dev] CIP IRC weekly meeting today
@ 2020-10-08  0:56 masashi.kudo
  2020-10-08  2:40 ` Kento Yoshida
                   ` (2 more replies)
  0 siblings, 3 replies; 195+ messages in thread
From: masashi.kudo @ 2020-10-08  0:56 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

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=10&day=8&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/10/cip.2020-10-01-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
      ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu 
      ->  Done, so will be closed today.

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5504): https://lists.cip-project.org/g/cip-dev/message/5504
Mute This Topic: https://lists.cip-project.org/mt/77375242/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-08  0:56 [cip-dev] CIP IRC weekly meeting today masashi.kudo
@ 2020-10-08  2:40 ` Kento Yoshida
  2020-10-08  5:46 ` Nobuhiro Iwamatsu
  2020-10-08  8:19 ` Chen-Yu Tsai (Moxa)
  2 siblings, 0 replies; 195+ messages in thread
From: Kento Yoshida @ 2020-10-08  2:40 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

Hi Kudo-san and all,

I'll be absent today.

And, I'll report here as an alternative to attendance.
Both minor updates were once reported, but since they are protracted, I will summarize again here.

Major updates:
 There is no major update this week.

Minor updates:
 1. Gap assessment for the development process (IEC 62443-4-1):
  The report from the certification body, whether development process for OSS meets to the IEC 62443-4-1 standard, is delayed.
  But, perhaps we can get it the end of this week.
  And then, we'll plan to share the documents on the development process that reflects the feedback from the report.
 2. Gap assessment for security features of security packages we suggested (IEC 62443-4-2):
  We started review security features of security packages we suggested to add as CIP core packages.
  The completion date is scheduled by the end of December.
  After this, we'll continue to proceed our suggestion, now it's pended.

Regards,
Kent

>-----Original Message-----
>From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of
>masashi.kudo@cybertrust.co.jp via lists.cip-project.org
>Sent: Thursday, October 8, 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&mont
>h=10&day=8&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=24
>1&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/10/cip.2020-10-01-09.00.log.htm
>l
>
>Agenda:
>
>* Action item
>  1. Combine root filesystem with kselftest binary - iwamatsu
>  2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
>      ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu
>      ->  Done, so will be closed today.
>
>* Kernel maintenance updates
>* Kernel testing
>* 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.


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5505): https://lists.cip-project.org/g/cip-dev/message/5505
Mute This Topic: https://lists.cip-project.org/mt/77375242/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-08  0:56 [cip-dev] CIP IRC weekly meeting today masashi.kudo
  2020-10-08  2:40 ` Kento Yoshida
@ 2020-10-08  5:46 ` Nobuhiro Iwamatsu
  2020-10-08  8:19 ` Chen-Yu Tsai (Moxa)
  2 siblings, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2020-10-08  5:46 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]

Hi Kudo-san,

Sorry, I can not participate 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, October 8, 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=10&day=8&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/10/cip.2020-10-01-09.00.log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu

No update.

>   2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
>       ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu
>       ->  Done, so will be closed today.
> 
> * Kernel maintenance updates

I reviewed 4.4.y-rc.

> * Kernel testing
> * 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


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5508): https://lists.cip-project.org/g/cip-dev/message/5508
Mute This Topic: https://lists.cip-project.org/mt/77375242/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-08  0:56 [cip-dev] CIP IRC weekly meeting today masashi.kudo
  2020-10-08  2:40 ` Kento Yoshida
  2020-10-08  5:46 ` Nobuhiro Iwamatsu
@ 2020-10-08  8:19 ` Chen-Yu Tsai (Moxa)
  2 siblings, 0 replies; 195+ messages in thread
From: Chen-Yu Tsai (Moxa) @ 2020-10-08  8:19 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Thu, Oct 8, 2020 at 8:57 AM masashi.kudo@cybertrust.co.jp
<masashi.kudo@cybertrust.co.jp> wrote:
>
> 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=10&day=8&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/10/cip.2020-10-01-09.00.log.html
>
> Agenda:
>
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
>       ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu
>       ->  Done, so will be closed today.
>
> * Kernel maintenance updates

I might not make it. Here's this week's update:

Five new CVEs:
- CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 [net/i40e] - Fixed for
mainline and 4.19+
  - This is enabled in Siemens x86 configs for both 4.4 and 4.19
    and we should probably backport them.
- CVE-2020-25643 [hdlc_ppp] - Fixed in all current stable kernels
- CVE-2020-26541 [UEFI secure boot] - Fix posted but hasn't landed

I also reviewed some patches from Daniel for cip-kernel-sec on the mailing list.

ChenYu



> * Kernel testing
> * 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.
>
>
> 
>

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5513): https://lists.cip-project.org/g/cip-dev/message/5513
Mute This Topic: https://lists.cip-project.org/mt/77375242/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-10-21 23:50 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-10-21 23:50 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

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=10&day=22&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/10/cip.2020-10-15-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Check whether CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 needs to be backported to 4.4 - masashi910

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5638): https://lists.cip-project.org/g/cip-dev/message/5638
Mute This Topic: https://lists.cip-project.org/mt/77720437/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-10-15  0:17 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-10-15  0:17 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

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=10&day=15&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/10/cip.2020-10-08-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Check whether CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 needs to be backported to 4.4 - masashi910

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5579): https://lists.cip-project.org/g/cip-dev/message/5579
Mute This Topic: https://lists.cip-project.org/mt/77518628/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-01  0:27 masashi.kudo
  2020-10-01  4:37 ` Chen-Yu Tsai (Moxa)
  2020-10-01  5:37 ` Chris Paterson
@ 2020-10-01  8:11 ` Pavel Machek
  2 siblings, 0 replies; 195+ messages in thread
From: Pavel Machek @ 2020-10-01  8:11 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]

Hi!

> 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=10&day=1&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

I may be able to make it, but in case I will not:

I reviewed 4.19.148 and 4.19.149.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5489): https://lists.cip-project.org/g/cip-dev/message/5489
Mute This Topic: https://lists.cip-project.org/mt/77230659/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-01  0:27 masashi.kudo
  2020-10-01  4:37 ` Chen-Yu Tsai (Moxa)
@ 2020-10-01  5:37 ` Chris Paterson
  2020-10-01  8:11 ` Pavel Machek
  2 siblings, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2020-10-01  5:37 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 1797 bytes --]

Hello Kudo-san,

Please accept my apologies for today's meeting.

From testing the only update I have is that lab-cip-renesas is back online now.

Kind regards, Chris
________________________________
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of masashi.kudo@cybertrust.co.jp via lists.cip-project.org <masashi.kudo=cybertrust.co.jp@lists.cip-project.org>
Sent: Thursday, October 1, 2020 1:27:21 AM
To: cip-dev@lists.cip-project.org <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=10&day=1&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/09/cip.2020-09-24-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu
  2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
      ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #1.2: Type: text/html, Size: 3644 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5488): https://lists.cip-project.org/g/cip-dev/message/5488
Mute This Topic: https://lists.cip-project.org/mt/77230659/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-10-01  0:27 masashi.kudo
@ 2020-10-01  4:37 ` Chen-Yu Tsai (Moxa)
  2020-10-01  5:37 ` Chris Paterson
  2020-10-01  8:11 ` Pavel Machek
  2 siblings, 0 replies; 195+ messages in thread
From: Chen-Yu Tsai (Moxa) @ 2020-10-01  4:37 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 1657 bytes --]

Hi,

It's the Mid-Autumn Festival, and we have a long weekend here.
So I will not be attending today's meeting.

3 new CVEs this week. Please check the merge request
In cip-kernel-sec for details.


ChenYu

masashi.kudo@cybertrust.co.jp <masashi.kudo@cybertrust.co.jp> 於 2020年10月1日
週四 08:54 寫道:

> 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=10&day=1&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/09/cip.2020-09-24-09.00.log.html
>
> Agenda:
>
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
>       ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config -
> iwamatsu
>
> * Kernel maintenance updates
> * Kernel testing
> * 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.
>
> 
>
>

[-- Attachment #1.2: Type: text/html, Size: 2795 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5487): https://lists.cip-project.org/g/cip-dev/message/5487
Mute This Topic: https://lists.cip-project.org/mt/77230659/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-10-01  0:27 masashi.kudo
  2020-10-01  4:37 ` Chen-Yu Tsai (Moxa)
                   ` (2 more replies)
  0 siblings, 3 replies; 195+ messages in thread
From: masashi.kudo @ 2020-10-01  0:27 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

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=10&day=1&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/09/cip.2020-09-24-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt
      ->  Delete rbd ( Ceph block device ) from 4.4-rt x86 config - iwamatsu 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5485): https://lists.cip-project.org/g/cip-dev/message/5485
Mute This Topic: https://lists.cip-project.org/mt/77230659/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-09-24  0:58 masashi.kudo
@ 2020-09-24  2:42 ` Akihiro Suzuki
  0 siblings, 0 replies; 195+ messages in thread
From: Akihiro Suzuki @ 2020-09-24  2:42 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

Hi Kudo-san,

Sorry, I will be absent IRC meeting today.
SW Updates WG don't have any updates this week.

Thanks,
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, September 24, 2020 9:59 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=9&day=24&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/09/cip.2020-09-17-09.00.log.
> html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt -
> masashi910
> 
> * Kernel maintenance updates
> * Kernel testing
> * 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.


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5469): https://lists.cip-project.org/g/cip-dev/message/5469
Mute This Topic: https://lists.cip-project.org/mt/77048514/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-09-24  0:58 masashi.kudo
  2020-09-24  2:42 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-09-24  0:58 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

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=9&day=24&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/09/cip.2020-09-17-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Check whether CVE-2020-25284 needs to be backported to 4.4-rt - masashi910 

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5468): https://lists.cip-project.org/g/cip-dev/message/5468
Mute This Topic: https://lists.cip-project.org/mt/77048514/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-09-17  1:20 masashi.kudo
@ 2020-09-17  6:58 ` Akihiro Suzuki
  0 siblings, 0 replies; 195+ messages in thread
From: Akihiro Suzuki @ 2020-09-17  6:58 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

Hi Kudo-san,

Sorry, I will be absent today's IRC meeting because I've got a plan already today.
SW Updates WG don't have any updates this week.

Thanks,
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, September 17, 2020 10:21 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=9&day=17&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/09/cip.2020-09-10-09.00.log.
> html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Post LTP results to KernelCI - patersonc
> 
> * Kernel maintenance updates
> * Kernel testing
> * Software update
> * CIP Security
> * AOB
> 
> Since there will be another meeting at 9:30GMT, the meeting will take less than
> 30 min today.
> If some topics may take long, they will be taken offline or in the next meeting.
> 
> Best regards,
> --
> M. Kudo
> Cybertrust Japan Co., Ltd.

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5460): https://lists.cip-project.org/g/cip-dev/message/5460
Mute This Topic: https://lists.cip-project.org/mt/76901376/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-09-17  1:20 masashi.kudo
  2020-09-17  6:58 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-09-17  1:20 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

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=9&day=17&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/09/cip.2020-09-10-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* Software update
* CIP Security 
* AOB

Since there will be another meeting at 9:30GMT, the meeting will take less than 30 min today.
If some topics may take long, they will be taken offline or in the next meeting.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5456): https://lists.cip-project.org/g/cip-dev/message/5456
Mute This Topic: https://lists.cip-project.org/mt/76901376/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-09-10  0:23 masashi.kudo
@ 2020-09-10  7:08 ` Nobuhiro Iwamatsu
  0 siblings, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2020-09-10  7:08 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

Hi Kudo-san,

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, September 10, 2020 9:23 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=9&day=10&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/09/cip.2020-09-03-09.00.log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu

No update.

>   2. Post LTP results to KernelCI - patersonc
> 
> * Kernel maintenance updates

I reviewed and pushed patches in cip-dev.

> * Kernel testing
> * 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,

Best regards,
  Nobuhiro


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5440): https://lists.cip-project.org/g/cip-dev/message/5440
Mute This Topic: https://lists.cip-project.org/mt/76745849/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-09-10  0:23 masashi.kudo
  2020-09-10  7:08 ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-09-10  0:23 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

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=9&day=10&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/09/cip.2020-09-03-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5439): https://lists.cip-project.org/g/cip-dev/message/5439
Mute This Topic: https://lists.cip-project.org/mt/76745849/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-09-03  0:09 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-09-03  0:09 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

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=9&day=3&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/08/cip.2020-08-27-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5386): https://lists.cip-project.org/g/cip-dev/message/5386
Mute This Topic: https://lists.cip-project.org/mt/76596395/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-08-27  0:58 masashi.kudo
@ 2020-08-27  5:04 ` Akihiro Suzuki
  0 siblings, 0 replies; 195+ messages in thread
From: Akihiro Suzuki @ 2020-08-27  5:04 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

Hi Kudo-san,

Sorry, I will be absent today's IRC meeting because I've got a plan already today.
SW Updates WG don't have any updates this week.

Thanks,
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, August 27, 2020 9:59 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=8&day=27&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/08/cip.2020-08-20-09.00.log.
> html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Post LTP results to KernelCI - patersonc
> 
> * Kernel maintenance updates
> * Kernel testing
> * 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5274): https://lists.cip-project.org/g/cip-dev/message/5274
Mute This Topic: https://lists.cip-project.org/mt/76442001/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-08-27  0:58 masashi.kudo
  2020-08-27  5:04 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-08-27  0:58 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

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=8&day=27&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/08/cip.2020-08-20-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5273): https://lists.cip-project.org/g/cip-dev/message/5273
Mute This Topic: https://lists.cip-project.org/mt/76442001/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-08-20  0:21 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-08-20  0:21 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

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=8&day=20&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/08/cip.2020-08-06-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5157): https://lists.cip-project.org/g/cip-dev/message/5157
Mute This Topic: https://lists.cip-project.org/mt/76298885/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-08-05 23:51 masashi.kudo
@ 2020-08-06  2:42 ` Akihiro Suzuki
  0 siblings, 0 replies; 195+ messages in thread
From: Akihiro Suzuki @ 2020-08-06  2:42 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

Hi Kudo-san,

Sorry, I will be absent today's IRC meeting because I've got a plan already today.
SW Updates WG don't have any updates 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, August 6, 2020 8:51 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=8&day=6&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/07/cip.2020-07-30-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5103): https://lists.cip-project.org/g/cip-dev/message/5103
Mute This Topic: https://lists.cip-project.org/mt/76018886/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-08-05 23:51 masashi.kudo
  2020-08-06  2:42 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-08-05 23:51 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

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=8&day=6&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/07/cip.2020-07-30-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5102): https://lists.cip-project.org/g/cip-dev/message/5102
Mute This Topic: https://lists.cip-project.org/mt/76018886/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-30  1:56 masashi.kudo
@ 2020-07-30  8:39 ` Akihiro Suzuki
  0 siblings, 0 replies; 195+ messages in thread
From: Akihiro Suzuki @ 2020-07-30  8:39 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

Hi Kudo-san,

I'm sorry I won't be able to join the IRC meeting today.
SW Updates WG still work on supporting HTTPS connection between SWUpdate and hawkBit.
https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8

Thanks,
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, July 30, 2020 10: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=7&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://lore.kernel.org/cip-dev/OSAPR01MB23857705B82D0D163B5E5211B7770@OSAPR01MB2385.jpnprd01.prod.outlook.com/T/#m873e67bf005078f86fe9f659682614def4a448a6

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Email Kernel team/cip-dev about patchwork usage - patersonc
Old AI "Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu" was taken care by SZ-san and was closed last week.

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5063): https://lists.cip-project.org/g/cip-dev/message/5063
Mute This Topic: https://lists.cip-project.org/mt/75878882/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-07-30  1:56 masashi.kudo
  2020-07-30  8:39 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-07-30  1:56 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

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=7&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://lore.kernel.org/cip-dev/OSAPR01MB23857705B82D0D163B5E5211B7770@OSAPR01MB2385.jpnprd01.prod.outlook.com/T/#m873e67bf005078f86fe9f659682614def4a448a6

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Email Kernel team/cip-dev about patchwork usage - patersonc
Old AI "Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu" was taken care by SZ-san and was closed last week.

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5057): https://lists.cip-project.org/g/cip-dev/message/5057
Mute This Topic: https://lists.cip-project.org/mt/75878882/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-23  2:58 masashi.kudo
  2020-07-23  7:32 ` Pavel Machek
@ 2020-07-24  8:27 ` Chris Paterson
  1 sibling, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2020-07-24  8:27 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 7281 bytes --]

Hello all,

The IRC logger was down yesterday, so please see a dirty copy/paste from the meeting below.

Kind regards, Chris

/start log

patersonc
Hello
wens
hi
szlin
hi
suzuki
hi
paveltest
hi
patersonc
I'm in charge today - sorry in advance!
#startmeeting CIP IRC weekly meeting
bwh joined the room.
bwh
hi
patersonc
#topic rollcall
Say hi etc.
(Doesn't look like the logger is working for me?)
dineshk
Hi
patersonc
I guess everyone has said hi already ;)
bwh
patersonc: It's not in the channel
patersonc
Ah
szlin
patersonc: it seems like the bot is not around
paveltest
Umm, I guess we can just pretend it works and create the logs manually or something.
patersonc
Sure
#topic AI review
Combine root filesystem with kselftest binary - iwamatsu
Any updates iwamatsu?
szlin
patersonc: Today is the national holiday in Japan
paveltest
I don't think he is around... did not say hi.
patersonc
Ah is it? I didn't realise :(
Moving on...
Post LTP results to KernelCI - patersonc
No updates from me
Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
szlin
Done
patersonc
Huzzah. Thanks szlin
szlin
I uploaded the new version of swupdate few weeks ago.
patersonc
Thanks. It could be that the action list I'm using is out of date...
Moving on...
#topic Kernel maintenance updates
wens
3 new CVEs, all fixed and backported (if needed); 3 old CVEs fixed.
paveltest
I have reviewed patches for 4.19.134.
bwh
I have reviewed kernel-sec updates by wens
patersonc
I have a question for the mainainers
Is anyone maintaining the CIP patchwork?
(or using)
paveltest
Hmm... We used it some time ago.
...but then I somehow forgot it exists.
patersonc
#link https://patchwork.kernel.org/project/cip-dev/list/
I wonder if someone should take ownership of it?
paveltest
Ammount of patches on the list is quite low, so patchwork is not really useful.
I believe we cna
can simply declare it dead.
It is currently not useful.
patersonc
Would it become more useful when LTS support ends?
paveltest
I don't think so.
It would become useful if we got a lot of patches
from participating companies.
patersonc
Any thoughts from anyone else?
paveltest
Currently we are just getting patches from Biju and ammount is quite low.
patersonc
Okay. Thanks 
paveltest
bwh
I don't have experience using patchwork, so I don't have a feel for when it's more or less useful
wens
I guess it really depends on the maintainers? It's less common for patch submitters to go on patchwork to update status for their own patches
(hence the unmaintained mess for lakml patchwork)
paveltest
I see patchwork as a service for patch submitters. If they are okay without it, it is easier for maintainer.
patersonc
I know that it's useful for those who want a nice URL to their submitted patch before it gets merged
wens
paveltest: I always thought it was the other way around.
patersonc: I believe lore takes care of that now
patersonc
I'll send an email to the wider maintainer/cip-dev group to see if everyone agrees that we should kill it, or leave it running (un)maintained
#action patersonc: Email Kernel team/cip-dev about patchwork usage
paveltest
Wens: well, if there are so many patches maintainer loses track, it is useful for maintainer too. But that is not currently the case.
patersonc
Any other topics/comments for/from the Kernel team?
5
4
3
2
1
#topic Kernel testing
KernelCI have agreed to add the CIP trees to kernelci.org
I've submitted a PR accordingly: https://github.com/kernelci/kernelci-core/pull/448
Fix renesas-soc repository and add CIP branches.
We also plan to have our own instance, initially running on KCI's servers at cip.kernelci.org.
Any testing related topics/questions from anyone else?
wens
are the instances completely separate, or sharing data / control?
patersonc
Separate. If we add any useful features on our fork we'd aim to upstream them back to kernelci
Initially we'd be using KCI's build infrastructure, with the aim of integrating it into our own
If anyone is interested in helping out with this effort please let me know.
Anyone for anymore before the next topic?
5
4
3
2
1
#topic Software update
suzuki
Hello.
I had found some problems with the current software update mechanism uploaded to cip-sw-updates-demo repository.
paveltest left the room.
suzuki
The problems had been that some needed files and settings didn't exist in the root file system.
I created gitlab issues about them: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/15, https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/16
And I'm working on them. One of them has been already done.
Apart from that, Mohammed is working on the task which is to support HTTPS connection between SWUpdate and hawkBit: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8
That's all from me.
patersonc
Thank you suzuki-san
Any queries from anyone?
5
4
3
2
1
#topic CIP Security
dineshk
hello
I guess Kent is not around so I will update
patersonc
Thank you
dineshk
Completed verification of single node security requirements on CIP LAVA
 Working with Chris to verify multi-node security requirements on LAVA
SOW signed with exida for CIP gap assessment for IEC-62443-4-2 & IEC-62443-4-1 
Kick-off meeting with exida held for Gap assessment yesterday
That's all from security WG
patersonc
Thank you dineshk
Any comments/queries?
5
4
3
2
1
#topic AOB
Any other topics from anyone today?
If not, then I guess we'll close for today.
Thank you all for your time!
#endmeeting

/end log 

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of masashi.kudo@cybertrust.co.jp via lists.cip-project.org
> Sent: 23 July 2020 03:59
> 
> Hi all,
> 
> Kindly be reminded to attend the weekly meeting through IRC to discuss
> technical topics with CIP kernel today.
> I cannot attend the meeting today. Chris-san will host the meeting instead.
> 
> *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=7&day=23&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=3
> 7&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/07/cip.2020-07-16-
> 09.00.log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Post LTP results to KernelCI - patersonc
>   3. Issues to be fixed for swupdate "copyright correction and salsa CI testing"
> - iwamatsu
> 
> * Kernel maintenance updates
> * Kernel testing
> * 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4994): https://lists.cip-project.org/g/cip-dev/message/4994
Mute This Topic: https://lists.cip-project.org/mt/75739176/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-23  2:58 masashi.kudo
@ 2020-07-23  7:32 ` Pavel Machek
  2020-07-24  8:27 ` Chris Paterson
  1 sibling, 0 replies; 195+ messages in thread
From: Pavel Machek @ 2020-07-23  7:32 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 492 bytes --]

Hi!

> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> I cannot attend the meeting today. Chris-san will host the meeting instead.
>

I should be able to attend the meeting, but in case reality
interferes:

I have reviewed patches for 4.19.134.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4982): https://lists.cip-project.org/g/cip-dev/message/4982
Mute This Topic: https://lists.cip-project.org/mt/75739176/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-07-23  2:58 masashi.kudo
  2020-07-23  7:32 ` Pavel Machek
  2020-07-24  8:27 ` Chris Paterson
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo @ 2020-07-23  2:58 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
I cannot attend the meeting today. Chris-san will host the meeting instead.

*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=7&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/07/cip.2020-07-16-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4981): https://lists.cip-project.org/g/cip-dev/message/4981
Mute This Topic: https://lists.cip-project.org/mt/75739176/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-16  1:29 masashi.kudo
  2020-07-16  6:11 ` Chen-Yu Tsai (Moxa)
@ 2020-07-16  8:27 ` Nobuhiro Iwamatsu
  1 sibling, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2020-07-16  8:27 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]

Hi,

I can't attend today's IRC meeting.

> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu

No update.
>   2. Post LTP results to KernelCI - patersonc
>   3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
> 
No update.

> * Kernel maintenance updates

I reviewed 4.4.y-rc patches.

Best regards,
  Nobuhiro

> -----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, July 16, 2020 10:30 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=7&day=16&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/07/cip.2020-07-09-09.00.log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Post LTP results to KernelCI - patersonc
>   3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
> 
> * Kernel maintenance updates
> * Kernel testing
> * 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4931): https://lists.cip-project.org/g/cip-dev/message/4931
Mute This Topic: https://lists.cip-project.org/mt/75533779/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-16  1:29 masashi.kudo
@ 2020-07-16  6:11 ` Chen-Yu Tsai (Moxa)
  2020-07-16  8:27 ` Nobuhiro Iwamatsu
  1 sibling, 0 replies; 195+ messages in thread
From: Chen-Yu Tsai (Moxa) @ 2020-07-16  6:11 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

Hi,

On Thu, Jul 16, 2020 at 9:30 AM masashi.kudo@cybertrust.co.jp
<masashi.kudo@cybertrust.co.jp> wrote:
>
> 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=7&day=16&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/07/cip.2020-07-09-09.00.log.html
>
> Agenda:
>
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu
>   2. Post LTP results to KernelCI - patersonc
>   3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
>
> * Kernel maintenance updates

I might not make it, so here are updates from me for this week:

Two new issues:

  - CVE-2020-11935 (aufs, not applicable to mainline)
  - CVE-2020-14314 (ext4 related, fix posted)


Regards
ChenYu

> * Kernel testing
> * 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.
> 

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4930): https://lists.cip-project.org/g/cip-dev/message/4930
Mute This Topic: https://lists.cip-project.org/mt/75533779/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-07-16  1:29 masashi.kudo
  2020-07-16  6:11 ` Chen-Yu Tsai (Moxa)
  2020-07-16  8:27 ` Nobuhiro Iwamatsu
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo @ 2020-07-16  1:29 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

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=7&day=16&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/07/cip.2020-07-09-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4929): https://lists.cip-project.org/g/cip-dev/message/4929
Mute This Topic: https://lists.cip-project.org/mt/75533779/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-08 22:42 masashi.kudo
@ 2020-07-09  7:06 ` Pavel Machek
  0 siblings, 0 replies; 195+ messages in thread
From: Pavel Machek @ 2020-07-09  7:06 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 520 bytes --]

Hi!

> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 

I am not sure if I'll be able to make it to the meeting.

My work last week: reviews of patches for 4.19.131 and 4.19.132. I
took a look at "PM / OPP v2 & cpufreq backports part 2" and will have
some comments there.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4915): https://lists.cip-project.org/g/cip-dev/message/4915
Mute This Topic: https://lists.cip-project.org/mt/75387533/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-07-08 22:42 masashi.kudo
  2020-07-09  7:06 ` Pavel Machek
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-07-08 22:42 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

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=7&day=9&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/07/cip.2020-07-02-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4912): https://lists.cip-project.org/g/cip-dev/message/4912
Mute This Topic: https://lists.cip-project.org/mt/75387533/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-02  8:43 ` Chris Paterson
@ 2020-07-02  8:49   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-07-02  8:49 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 2287 bytes --]

Hi, Chris-san,

Sure, then see you at the CIP mini summit!

Best regards,
--
M. Kudo

From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Chris Paterson
Sent: Thursday, July 2, 2020 5:44 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hello Kudo-san,
Please accept my apologies; I can't babe the meeting this week.
Kind regards, Chris
________________________________
From: cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>> on behalf of masashi.kudo@cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp> via lists.cip-project.org <masashi.kudo=cybertrust.co.jp@lists.cip-project.org<mailto:masashi.kudo=cybertrust.co.jp@lists.cip-project.org>>
Sent: Wednesday, July 1, 2020 11:53:32 PM
To: cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev@lists.cip-project.org<mailto: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=7&day=2&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/06/cip.2020-06-25-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu
  2. Post LTP results to KernelCI - patersonc
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #1.2: Type: text/html, Size: 7359 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4882): https://lists.cip-project.org/g/cip-dev/message/4882
Mute This Topic: https://lists.cip-project.org/mt/75247269/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-07-01 22:53 masashi.kudo
@ 2020-07-02  8:43 ` Chris Paterson
  2020-07-02  8:49   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Chris Paterson @ 2020-07-02  8:43 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 1722 bytes --]

Hello Kudo-san,

Please accept my apologies; I can't babe the meeting this week.

Kind regards, Chris
________________________________
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of masashi.kudo@cybertrust.co.jp via lists.cip-project.org <masashi.kudo=cybertrust.co.jp@lists.cip-project.org>
Sent: Wednesday, July 1, 2020 11:53:32 PM
To: cip-dev@lists.cip-project.org <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=7&day=2&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/06/cip.2020-06-25-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu
  2. Post LTP results to KernelCI - patersonc
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #1.2: Type: text/html, Size: 3283 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4881): https://lists.cip-project.org/g/cip-dev/message/4881
Mute This Topic: https://lists.cip-project.org/mt/75247269/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-07-01 22:53 masashi.kudo
  2020-07-02  8:43 ` Chris Paterson
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-07-01 22:53 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

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=7&day=2&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/06/cip.2020-06-25-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4878): https://lists.cip-project.org/g/cip-dev/message/4878
Mute This Topic: https://lists.cip-project.org/mt/75247269/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-25  7:00 ` Pavel Machek
@ 2020-06-25  7:03   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-25  7:03 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 200 bytes --]

Hi, Pavel-san,

> Not sure if I'll be able to make it today.
> From last meeting, I have been reviewing patches for 4.19.129 and 4.19.130.

Thanks for your update.

Best regards,
--
M. Kudo

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4812): https://lists.cip-project.org/g/cip-dev/message/4812
Mute This Topic: https://lists.cip-project.org/mt/75095440/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-25  1:53 masashi.kudo
@ 2020-06-25  7:00 ` Pavel Machek
  2020-06-25  7:03   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Pavel Machek @ 2020-06-25  7:00 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 840 bytes --]

Hi!

> 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=6&day=25&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

Not sure if I'll be able to make it today.

From last meeting, I have been reviewing patches for 4.19.129 and
4.19.130.

Best regards,
                                                                        Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4811): https://lists.cip-project.org/g/cip-dev/message/4811
Mute This Topic: https://lists.cip-project.org/mt/75095440/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-06-25  1:53 masashi.kudo
  2020-06-25  7:00 ` Pavel Machek
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-06-25  1:53 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

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=6&day=25&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/06/cip.2020-06-18-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Ask board owners to review reference platform configs to optimize backporting - masashi910
  4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu
  5. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4810): https://lists.cip-project.org/g/cip-dev/message/4810
Mute This Topic: https://lists.cip-project.org/mt/75095440/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-18  7:19 ` Nobuhiro Iwamatsu
@ 2020-06-18  7:27   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-18  7:27 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]

Hi, Iwamatsu-san,

Thanks for your updates. But, how about the following?

>   5. Issues to be fixed for swupdate "copyright correction and salsa 
> CI testing" - iwamatsu

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, June 18, 2020 4:19 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi,

I can not attend IRC meeting today, sorry.

> -----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, June 18, 2020 9:20 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=6&day=18&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/06/cip.2020-06-11-09.00
> .log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu

No update.

>   2. Post LTP results to KernelCI - patersonc
>   3. Ask board owners to review reference platform configs to optimize backporting - masashi910
>   4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - 
> iwamatsu

No update.
No update  / work can be seen even in Upstream etc.

>   5. Issues to be fixed for swupdate "copyright correction and salsa 
> CI testing" - iwamatsu
> 
> Note: The followings are 2020 Kernel Team Roadmap stuff. If there are 
> any progresses I will report at the "Kernel maintenance updates" in future.
>   +. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
>   +. Upload a guideline for reference hardware platform addition - 
> masashi910
> 
> * Kernel maintenance updates

I reviewed LTS-rc. I send a comment.

> * Kernel testing
> * 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

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

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4804): https://lists.cip-project.org/g/cip-dev/message/4804
Mute This Topic: https://lists.cip-project.org/mt/74949757/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-18  0:20 masashi.kudo
  2020-06-18  2:12 ` masashi.kudo
@ 2020-06-18  7:19 ` Nobuhiro Iwamatsu
  2020-06-18  7:27   ` masashi.kudo
  1 sibling, 1 reply; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2020-06-18  7:19 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]

Hi,

I can not attend IRC meeting today, sorry.

> -----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, June 18, 2020 9:20 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=6&day=18&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/06/cip.2020-06-11-09.00.log.html
> 
> Agenda:
> 
> * Action item
>   1. Combine root filesystem with kselftest binary - iwamatsu

No update.

>   2. Post LTP results to KernelCI - patersonc
>   3. Ask board owners to review reference platform configs to optimize backporting - masashi910
>   4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu

No update.
No update  / work can be seen even in Upstream etc.

>   5. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu
> 
> Note: The followings are 2020 Kernel Team Roadmap stuff. If there are any progresses I will report at the "Kernel
> maintenance updates" in future.
>   +. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
>   +. Upload a guideline for reference hardware platform addition - masashi910
> 
> * Kernel maintenance updates

I reviewed LTS-rc. I send a comment.

> * Kernel testing
> * 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

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

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4803): https://lists.cip-project.org/g/cip-dev/message/4803
Mute This Topic: https://lists.cip-project.org/mt/74949757/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-06-18  0:20 masashi.kudo
@ 2020-06-18  2:12 ` masashi.kudo
  2020-06-18  7:19 ` Nobuhiro Iwamatsu
  1 sibling, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-18  2:12 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

Hi, all, 

Please let me resend, because the original mail does not seem to be delivered.

Best regards,
--
M. Kudo

-----Original Message-----
From: 工藤 雅司(CTJ OSS事業推進室) 
Sent: Thursday, June 18, 2020 9:20 AM
To: cip-dev@lists.cip-project.org
Subject: 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=6&day=18&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/06/cip.2020-06-11-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Ask board owners to review reference platform configs to optimize backporting - masashi910
  4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu
  5. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

Note: The followings are 2020 Kernel Team Roadmap stuff. If there are any progresses I will report at the "Kernel maintenance updates" in future.
  +. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  +. Upload a guideline for reference hardware platform addition - masashi910

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4802): https://lists.cip-project.org/g/cip-dev/message/4802
Mute This Topic: https://lists.cip-project.org/mt/74949757/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-06-18  0:20 masashi.kudo
  2020-06-18  2:12 ` masashi.kudo
  2020-06-18  7:19 ` Nobuhiro Iwamatsu
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-18  0:20 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]

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=6&day=18&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/06/cip.2020-06-11-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Post LTP results to KernelCI - patersonc 
  3. Ask board owners to review reference platform configs to optimize backporting - masashi910
  4. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu
  5. Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu

Note: The followings are 2020 Kernel Team Roadmap stuff. If there are any progresses I will report at the "Kernel maintenance updates" in future.
  +. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  +. Upload a guideline for reference hardware platform addition - masashi910

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4801): https://lists.cip-project.org/g/cip-dev/message/4801
Mute This Topic: https://lists.cip-project.org/mt/74949757/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-11 11:23 ` Pavel Machek
@ 2020-06-11 11:47   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-11 11:47 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

Hi, Pavel-san,

> I'll go	through	the IRC	logs.

The log is the following.
https://irclogs.baserock.org/meetings/cip/2020/06/cip.2020-06-11-09.00.log.html

Best regards,
--
M. Kudo

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Pavel Machek
Sent: Thursday, June 11, 2020 8:24 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi!


> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 

I'm sorry I missed the meeting. I'll go	through	the IRC	logs.

My activity last week: reviews on 4.19.127 and patches queued for 4.19.128.

Best regards,
     								Pavel


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4795): https://lists.cip-project.org/g/cip-dev/message/4795
Mute This Topic: https://lists.cip-project.org/mt/74808947/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-10 23:55 masashi.kudo
@ 2020-06-11 11:23 ` Pavel Machek
  2020-06-11 11:47   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Pavel Machek @ 2020-06-11 11:23 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

Hi!


> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 

I'm sorry I missed the meeting. I'll go	through	the IRC	logs.

My activity last week: reviews on 4.19.127 and patches queued for 4.19.128.

Best regards,
     								Pavel


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4794): https://lists.cip-project.org/g/cip-dev/message/4794
Mute This Topic: https://lists.cip-project.org/mt/74808947/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-06-10 23:55 masashi.kudo
  2020-06-11 11:23 ` Pavel Machek
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-06-10 23:55 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

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=6&day=11&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/06/cip.2020-06-04-09.00.log.html

Agenda:

* Action item
  1. Combine root filesystem with kselftest binary - iwamatsu 
  2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  3. Upload a guideline for reference hardware platform addition - masashi910
  4. Post LTP results to KernelCI - patersonc 
  5. Ask board owners to review reference platform configs to optimize backporting - masashi910
  6. Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - iwamatsu

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4793): https://lists.cip-project.org/g/cip-dev/message/4793
Mute This Topic: https://lists.cip-project.org/mt/74808947/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-04  6:58 ` Akihiro Suzuki
@ 2020-06-04  7:12   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-06-04  7:12 UTC (permalink / raw)
  To: akihiro27.suzuki; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]

Hi, Suzuki-san,

Noted. See you next week.

Best regards,
--
M. Kudo

-----Original Message-----
From: akihiro27.suzuki@toshiba.co.jp <akihiro27.suzuki@toshiba.co.jp> 
Sent: Thursday, June 4, 2020 3:58 PM
To: 工藤 雅司(CTJ OSS事業推進室) <masashi.kudo@cybertrust.co.jp>
Cc: cip-dev@lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi Kudo-san,

Sorry, I got a plan today. So I'll be absent today's IRC meeting.
SW Updates WG doesn't have any updates since last 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, June 4, 2020 11:39 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=6&day=4&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-28-09.00.log.html

Agenda:

* Action item
  1.  Combine root filesystem with kselftest binary - iwamatsu 
  2.  Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  3.  Upload a guideline for reference hardware platform addition - masashi910
  4.  Post LTP results to KernelCI - patersonc 
  5.  Ask board owners to review reference platform configs to optimize backporting - masashi910
  6.  Check CVE and Patch: NFS client (CVE-2020-10742)  - Pavel-san
  7.  Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4695): https://lists.cip-project.org/g/cip-dev/message/4695
Mute This Topic: https://lists.cip-project.org/mt/74664504/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-06-04  2:38 masashi.kudo
@ 2020-06-04  6:58 ` Akihiro Suzuki
  2020-06-04  7:12   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Akihiro Suzuki @ 2020-06-04  6:58 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

Hi Kudo-san,

Sorry, I got a plan today. So I'll be absent today's IRC meeting.
SW Updates WG doesn't have any updates since last 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, June 4, 2020 11:39 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=6&day=4&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-28-09.00.log.html

Agenda:

* Action item
  1.  Combine root filesystem with kselftest binary - iwamatsu 
  2.  Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  3.  Upload a guideline for reference hardware platform addition - masashi910
  4.  Post LTP results to KernelCI - patersonc 
  5.  Ask board owners to review reference platform configs to optimize backporting - masashi910
  6.  Check CVE and Patch: NFS client (CVE-2020-10742)  - Pavel-san
  7.  Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4694): https://lists.cip-project.org/g/cip-dev/message/4694
Mute This Topic: https://lists.cip-project.org/mt/74664504/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-06-04  2:38 masashi.kudo
  2020-06-04  6:58 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-06-04  2:38 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

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=6&day=4&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-28-09.00.log.html

Agenda:

* Action item
  1.  Combine root filesystem with kselftest binary - iwamatsu 
  2.  Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
  3.  Upload a guideline for reference hardware platform addition - masashi910
  4.  Post LTP results to KernelCI - patersonc 
  5.  Ask board owners to review reference platform configs to optimize backporting - masashi910
  6.  Check CVE and Patch: NFS client (CVE-2020-10742)  - Pavel-san
  7.  Check CVE and Patch, Bluetooth BAIS attack (CVE-2020-10135) - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4672): https://lists.cip-project.org/g/cip-dev/message/4672
Mute This Topic: https://lists.cip-project.org/mt/74664504/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-05-28  1:26 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-05-28  1:26 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

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=5&day=28&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-21-09.00.log.html

Agenda:
Starting this week, "CIP Core" session is not covered in IRC meetings.
We will invite the Core team as needed basis.

* Action item
 1. Combine root filesystem with kselftest binary - iwamatsu 
 2. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
 3. Upload a guideline for reference hardware platform addition - masashi910
 4. Post LTP results to KernelCI - patersonc 
 5. Ask board owners to review reference platform configs to optimize backporting - masashi910 

* Kernel maintenance updates
* Kernel testing
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4650): https://lists.cip-project.org/g/cip-dev/message/4650
Mute This Topic: https://lists.cip-project.org/mt/74513780/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-05-21  6:08 ` Nobuhiro Iwamatsu
@ 2020-05-21  7:12   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-05-21  7:12 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2464 bytes --]

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


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4638): https://lists.cip-project.org/g/cip-dev/message/4638
Mute This Topic: https://lists.cip-project.org/mt/74364606/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-05-21  0:36 masashi.kudo
@ 2020-05-21  6:08 ` Nobuhiro Iwamatsu
  2020-05-21  7:12   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2020-05-21  6:08 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]

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&month=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


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4637): https://lists.cip-project.org/g/cip-dev/message/4637
Mute This Topic: https://lists.cip-project.org/mt/74364606/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-05-21  0:36 masashi.kudo
  2020-05-21  6:08 ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-05-21  0:36 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

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=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 
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
* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4635): https://lists.cip-project.org/g/cip-dev/message/4635
Mute This Topic: https://lists.cip-project.org/mt/74364606/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-05-13 23:27 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-05-13 23:27 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

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=5&day=14&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-07-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
3. Upload a guideline for reference hardware platform addition - masashi910
4. Propose a reduction of kernel repository mirrors to TSC  - masashi910
5. Post LTP results to KernelCI - patersonc 

* 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.


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4620): https://lists.cip-project.org/g/cip-dev/message/4620
Mute This Topic: https://lists.cip-project.org/mt/74194672/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-05-06 22:28 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-05-06 22:28 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

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=5&day=7&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-30-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
3. Upload a guideline for reference hardware platform addition - masashi910

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

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4616): https://lists.cip-project.org/g/cip-dev/message/4616
Mute This Topic: https://lists.cip-project.org/mt/74039675/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-23  8:41 ` Akihiro Suzuki
@ 2020-04-23  8:43   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-23  8:43 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]

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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4598): https://lists.cip-project.org/g/cip-dev/message/4598
Mute This Topic: https://lists.cip-project.org/mt/73209616/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-23  0:06 masashi.kudo
@ 2020-04-23  8:41 ` Akihiro Suzuki
  2020-04-23  8:43   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: Akihiro Suzuki @ 2020-04-23  8:41 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4597): https://lists.cip-project.org/g/cip-dev/message/4597
Mute This Topic: https://lists.cip-project.org/mt/73209616/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-04-23  0:06 masashi.kudo
  2020-04-23  8:41 ` Akihiro Suzuki
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-04-23  0:06 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4596): https://lists.cip-project.org/g/cip-dev/message/4596
Mute This Topic: https://lists.cip-project.org/mt/73209616/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-16  8:15 ` Chris Paterson
@ 2020-04-16  8:18   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-16  8:18 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 2750 bytes --]

Hi, Chris-san,

Sure, please rest at ease, and stay safe. See you next week.

Best regards,
--
M. Kudo

From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Chris Paterson
Sent: Thursday, April 16, 2020 5:16 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hello Kudo-san,
Please accept my apologies for today's meeting as I am on leave this week.
No major updates to report from the testing working group.
Kind regards, Chris
________________________________
From: cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>> on behalf of masashi.kudo@cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp> via lists.cip-project.org <masashi.kudo=cybertrust.co.jp@lists.cip-project.org<mailto:masashi.kudo=cybertrust.co.jp@lists.cip-project.org>>
Sent: Thursday, April 16, 2020 3:02:49 AM
To: cip-dev@lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev@lists.cip-project.org<mailto: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=16&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-09-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
5. Clarify the requirement about system-backup - Yoshida-san

* 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.

[-- Attachment #1.2: Type: text/html, Size: 8001 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4582): https://lists.cip-project.org/g/cip-dev/message/4582
Mute This Topic: https://lists.cip-project.org/mt/73047683/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-16  2:02 masashi.kudo
  2020-04-16  7:21 ` punit1.agrawal
@ 2020-04-16  8:15 ` Chris Paterson
  2020-04-16  8:18   ` masashi.kudo
  1 sibling, 1 reply; 195+ messages in thread
From: Chris Paterson @ 2020-04-16  8:15 UTC (permalink / raw)
  To: cip-dev

[-- Attachment #1.1: Type: text/plain, Size: 2167 bytes --]

Hello Kudo-san,

Please accept my apologies for today's meeting as I am on leave this week.

No major updates to report from the testing working group.

Kind regards, Chris
________________________________
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of masashi.kudo@cybertrust.co.jp via lists.cip-project.org <masashi.kudo=cybertrust.co.jp@lists.cip-project.org>
Sent: Thursday, April 16, 2020 3:02:49 AM
To: cip-dev@lists.cip-project.org <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=16&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-09-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
5. Clarify the requirement about system-backup - Yoshida-san

* 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.

[-- Attachment #1.2: Type: text/html, Size: 3835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4581): https://lists.cip-project.org/g/cip-dev/message/4581
Mute This Topic: https://lists.cip-project.org/mt/73047683/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-16  7:21 ` punit1.agrawal
@ 2020-04-16  7:28   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-16  7:28 UTC (permalink / raw)
  To: punit1.agrawal; +Cc: cip-dev, daniel.sangorrin


[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

Hi, Punit-san,

Thanks for letting me know the status. See you next week!

Best regards,
--
M. Kudo

-----Original Message-----
From: Punit Agrawal <punit1.agrawal@toshiba.co.jp> 
Sent: Thursday, April 16, 2020 4:22 PM
To: 工藤 雅司(CTJ OSS事業推進室) <masashi.kudo@cybertrust.co.jp>
Cc: cip-dev@lists.cip-project.org; Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi Kudo-san,

I won't be able to attend the meeting today. Some updates below -

"masashi.kudo@cybertrust.co.jp" <masashi.kudo@cybertrust.co.jp> writes:

[...]

> * CIP Core

- Discussion around projected EOL for CIP core support on cip-dev. Based
  on the comments in the TSC I will update the proposal to YYYY-MM
  format.
- Daniel to take over CIP Core activities going forward

Thanks,
Punit

[...]


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4580): https://lists.cip-project.org/g/cip-dev/message/4580
Mute This Topic: https://lists.cip-project.org/mt/73047683/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-16  2:02 masashi.kudo
@ 2020-04-16  7:21 ` punit1.agrawal
  2020-04-16  7:28   ` masashi.kudo
  2020-04-16  8:15 ` Chris Paterson
  1 sibling, 1 reply; 195+ messages in thread
From: punit1.agrawal @ 2020-04-16  7:21 UTC (permalink / raw)
  To: masashi.kudo; +Cc: cip-dev, Daniel Sangorrin


[-- Attachment #1: Type: text/plain, Size: 404 bytes --]

Hi Kudo-san,

I won't be able to attend the meeting today. Some updates below -

"masashi.kudo@cybertrust.co.jp" <masashi.kudo@cybertrust.co.jp> writes:

[...]

> * CIP Core

- Discussion around projected EOL for CIP core support on cip-dev. Based
  on the comments in the TSC I will update the proposal to YYYY-MM
  format.
- Daniel to take over CIP Core activities going forward

Thanks,
Punit

[...]


[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4579): https://lists.cip-project.org/g/cip-dev/message/4579
Mute This Topic: https://lists.cip-project.org/mt/73047683/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-04-16  2:02 masashi.kudo
  2020-04-16  7:21 ` punit1.agrawal
  2020-04-16  8:15 ` Chris Paterson
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-16  2:02 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

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=16&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-09-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
5. Clarify the requirement about system-backup - Yoshida-san

* 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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4578): https://lists.cip-project.org/g/cip-dev/message/4578
Mute This Topic: https://lists.cip-project.org/mt/73047683/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-04-08 23:24 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-08 23:24 UTC (permalink / raw)
  To: cip-dev


[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

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=9&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-02-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.

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4568): https://lists.cip-project.org/g/cip-dev/message/4568
Mute This Topic: https://lists.cip-project.org/mt/72886394/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-02  8:19 ` nobuhiro1.iwamatsu
@ 2020-04-02  8:22   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-04-02  8:22 UTC (permalink / raw)
  To: nobuhiro1.iwamatsu, cip-dev

Hi, Iwamatsu-san,

Noted. Then, see you next week!

Best regards,
--
M. Kudo

-----Original Message-----
From: nobuhiro1.iwamatsu@toshiba.co.jp <nobuhiro1.iwamatsu@toshiba.co.jp> 
Sent: Thursday, April 2, 2020 5:19 PM
To: 工藤 雅司(CTJ OSS事業推進室) <masashi.kudo@cybertrust.co.jp>; cip-dev@lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi,

Sorry, I can not join IRC meeting today.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces@lists.cip-project.org] On Behalf 
> Of masashi.kudo@cybertrust.co.jp
> Sent: Thursday, April 2, 2020 9:30 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=2&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/03/cip.2020-03-26-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  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
> 
> * Kernel maintenance updates

No update. But I reviewed and checked other LTS kernel.

> * 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
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-04-02  0:30 masashi.kudo
@ 2020-04-02  8:19 ` nobuhiro1.iwamatsu
  2020-04-02  8:22   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: nobuhiro1.iwamatsu @ 2020-04-02  8:19 UTC (permalink / raw)
  To: masashi.kudo, cip-dev

Hi,

Sorry, I can not join IRC meeting today.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces@lists.cip-project.org] On Behalf
> Of masashi.kudo@cybertrust.co.jp
> Sent: Thursday, April 2, 2020 9:30 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=2&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/03/cip.2020-03-26-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  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
> 
> * Kernel maintenance updates

No update. But I reviewed and checked other LTS kernel.

> * 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
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-04-02  0:30 masashi.kudo
  2020-04-02  8:19 ` nobuhiro1.iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-04-02  0:30 UTC (permalink / raw)
  To: cip-dev

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=2&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/03/cip.2020-03-26-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

* 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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-03-25 22:52 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-03-25 22:52 UTC (permalink / raw)
  To: cip-dev

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=3&day=26&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-19-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 
2. Assign the owner of "CIP kernel config" - masashi910
3. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
 3-1. Workflow for identifying important fixes, backporting, and reviewing them
 3-2. Prepare the tools to be used for this workflow
 3-3. Get practice in backporting patches
4. Upload a guideline for reference hardware platform addition - masashi910

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* CIP Security 
* AOB
1. Summer Time
US summer time started on March 8. CEST starts on March 29. This IRC meeting stays to start at UTC (GMT) 09:00.

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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-03-19  8:17 ` nobuhiro1.iwamatsu
@ 2020-03-19  8:20   ` masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-03-19  8:20 UTC (permalink / raw)
  To: nobuhiro1.iwamatsu, cip-dev

Hi, Iwamatsu-san,

Thanks for your updates! Also thanks for your offer about #AI-2!
We will discuss this in the IRC.

Best regards,
--
M. Kudo

-----Original Message-----
From: nobuhiro1.iwamatsu@toshiba.co.jp <nobuhiro1.iwamatsu@toshiba.co.jp> 
Sent: Thursday, March 19, 2020 5:17 PM
To: 工藤 雅司(CTJ) <masashi.kudo@cybertrust.co.jp>; cip-dev@lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi Kudo-san,

I can't attend IRC meetings today.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces@lists.cip-project.org] On Behalf 
> Of masashi.kudo@cybertrust.co.jp
> Sent: Thursday, March 19, 2020 7:36 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=3&day=19&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241
> &p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 02:00    05:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-12-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine root filesystem with kselftest binary - Iwamatsu-san

No update.

> 2. Assign the owner of "CIP kernel config" - masashi910

Note; If no one is owner, I can do it.

3. Strengthen sustainable
> process to backport patches from Mainline/LTS - Kernel Team  3-1.
> Workflow for identifying important fixes, backporting, and reviewing 
> them 3-2. Prepare the tools to be used for this workflow  3-3. Get 
> practice in backporting patches 4. Upload a guideline for reference 
> hardware platform addition - masashi910
> 
> * Kernel maintenance updates

I was late, I released new CIP kernels.
  https://lists.cip-project.org/pipermail/cip-dev/2020-March/004516.html

> * Kernel testing
> * CIP Core
> * Software update
> * AOB
> 1. Summer Time
> US summer time started on March 8. CEST starts on March 29.
> This IRC meeting starts at UTC (GMT) 09:00.
> 
> 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

_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* Re: [cip-dev] CIP IRC weekly meeting today
  2020-03-18 22:35 masashi.kudo
@ 2020-03-19  8:17 ` nobuhiro1.iwamatsu
  2020-03-19  8:20   ` masashi.kudo
  0 siblings, 1 reply; 195+ messages in thread
From: nobuhiro1.iwamatsu @ 2020-03-19  8:17 UTC (permalink / raw)
  To: masashi.kudo, cip-dev

Hi Kudo-san,

I can't attend IRC meetings today.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces@lists.cip-project.org] On Behalf
> Of masashi.kudo@cybertrust.co.jp
> Sent: Thursday, March 19, 2020 7:36 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=3&day=19&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241
> &p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 02:00    05:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-12-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine root filesystem with kselftest binary - Iwamatsu-san 

No update.

> 2. Assign the owner of "CIP kernel config" - masashi910 

Note; If no one is owner, I can do it.

3. Strengthen sustainable
> process to backport patches from Mainline/LTS - Kernel Team  3-1.
> Workflow for identifying important fixes, backporting, and reviewing them
> 3-2. Prepare the tools to be used for this workflow  3-3. Get practice
> in backporting patches 4. Upload a guideline for reference hardware
> platform addition - masashi910
> 
> * Kernel maintenance updates

I was late, I released new CIP kernels.
  https://lists.cip-project.org/pipermail/cip-dev/2020-March/004516.html

> * Kernel testing
> * CIP Core
> * Software update
> * AOB
> 1. Summer Time
> US summer time started on March 8. CEST starts on March 29.
> This IRC meeting starts at UTC (GMT) 09:00.
> 
> 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

_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-03-18 22:35 masashi.kudo
  2020-03-19  8:17 ` nobuhiro1.iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo @ 2020-03-18 22:35 UTC (permalink / raw)
  To: cip-dev

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=3&day=19&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-12-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 
2. Assign the owner of "CIP kernel config" - masashi910
3. Strengthen sustainable process to backport patches from Mainline/LTS - Kernel Team
 3-1. Workflow for identifying important fixes, backporting, and reviewing them
 3-2. Prepare the tools to be used for this workflow
 3-3. Get practice in backporting patches
4. Upload a guideline for reference hardware platform addition - masashi910

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Summer Time
US summer time started on March 8. CEST starts on March 29.
This IRC meeting starts at UTC (GMT) 09:00.

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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-03-11 23:42 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-03-11 23:42 UTC (permalink / raw)
  To: cip-dev

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=3&day=12&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/03/cip.2020-03-05-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 
2. Assign the owner of "CIP kernel config" - masashi910
3. Refine statistics figures of Kernel Team contributions to upstream (LTS) - masashi910
4. Strengthen sustainable process to backport patches from Mainline/LTS - TBD
 4-1. Workflow for identifying important fixes, backporting, and reviewing them
 4-2. Prepare the tools to be used for this workflow
 4-3. Get practice in backporting patches
5. Upload a guideline for reference hardware platform addition - masashi910

The following action item was defined at the team call on Feb 27th.
We will work on this when time comes.
  x. Explore the possibilities to work on security fixes proactively

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Summer Time
US summer time started on March 8. CEST starts on March 29.
This IRC meeting starts at UTC (GMT) 09:00.

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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-03-05  0:28 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-03-05  0:28 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-20-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 

Additional action items were identified at the team call last week.
I am preparing to list them here. Please wait for a moment to appear them.

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Migratoin from Mailman2 to Groupio
Any opinion about the migration timing from Mailman2 to Groups.io?
Excerpt from a mail of Linux Foundation:
+++
We are now ready to migrate from Mailman2 to Groups.io . cip-dev archives are already being hosted at lore.kernel.org, and when we perform the migration they will continue to be hosted on that site, there is nothing more we need to do. 
Linux Foundation IT needs about 3 weeks or more notice to coordinate the migration. 
There will be as much as 24 hours downtime for all the CIP lists, however, emails will be queued up and not lost, during that time. When Groups.io comes back up, the emails will come through. 
+++

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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-02-19 23:09 masashi.kudo
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo @ 2020-02-19 23:09 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-13-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Cancellation of "F2F" meetings in Nuremberg
2. "F2F" Kernel Team Meeting is now Kernel Team "Call" which will be held as follows. 
TZ:	Tokyo	Taipei	Berlin	London	NY	LA
----------------------------------------------------------
Start:	21:00	20:00	13:00	12:00	07:00	04:00
End:	22:00	21:00	14:00	13:00	08:00 	05:00

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.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-02-13  1:31 masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-02-13  1:31 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-06-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-02-06  7:25 ` nobuhiro1.iwamatsu at toshiba.co.jp
@ 2020-02-06  8:04   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-02-06  8:04 UTC (permalink / raw)
  To: cip-dev

Hi, Iwamatsu-san,

Thanks for letting us know your updates.
Then, see you next week!

Best regards,
--
M. Kudo

-----Original Message-----
From: nobuhiro1.iwamatsu@toshiba.co.jp <nobuhiro1.iwamatsu@toshiba.co.jp> 
Sent: Thursday, February 6, 2020 4:25 PM
To: ??????CTJ? <masashi.kudo@cybertrust.co.jp>; cip-dev at lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi Kudo-san,

I may not be able to join IRC meeting today.

> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san

No update.

> 2. Document a process on how to add tests to the CIP test setup - 
> patersonc 3. Arrangement of F2F Kernel Meeting in Nuremberg - 
> masashi910 4. Add config for BBB to both 4.4 and 4.19 (done for 
> qemux86-64)  - Iwamatsu-san
> 

These already was applied to cip-kernel-config repository. Please close this A.I.

> * Kernel maintenance updates

I reviewed 4.4.212 and 213.

Best regards,
  Nobuhiro

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf 
> Of masashi.kudo at cybertrust.co.jp
> Sent: Thursday, February 6, 2020 7:58 AM
> To: cip-dev at 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=3
> 7&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 2. 
> Document a process on how to add tests to the CIP test setup - 
> patersonc 3. Arrangement of F2F Kernel Meeting in Nuremberg - 
> masashi910 4. Add config for BBB to both 4.4 and 4.19 (done for 
> qemux86-64)  - Iwamatsu-san
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-02-05 22:58 masashi.kudo at cybertrust.co.jp
@ 2020-02-06  7:25 ` nobuhiro1.iwamatsu at toshiba.co.jp
  2020-02-06  8:04   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2020-02-06  7:25 UTC (permalink / raw)
  To: cip-dev

Hi Kudo-san,

I may not be able to join IRC meeting today.

> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san

No update.

> 2. Document a process on how to add tests to the CIP test setup - patersonc
> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
> 4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san
> 

These already was applied to cip-kernel-config repository. Please close this A.I.

> * Kernel maintenance updates

I reviewed 4.4.212 and 213.

Best regards,
  Nobuhiro

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf
> Of masashi.kudo at cybertrust.co.jp
> Sent: Thursday, February 6, 2020 7:58 AM
> To: cip-dev at 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=3
> 7&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san
> 2. Document a process on how to add tests to the CIP test setup - patersonc
> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
> 4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-02-05 22:58 masashi.kudo at cybertrust.co.jp
  2020-02-06  7:25 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-02-05 22:58 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 
3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-29 22:54 masashi.kudo at cybertrust.co.jp
  2020-01-30  7:35 ` Chris Paterson
@ 2020-01-30 13:29 ` masashi.kudo at cybertrust.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-30 13:29 UTC (permalink / raw)
  To: cip-dev

Hi, all,

> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910

Yoshi-san just confirmed that the F2F Kernel Meeting time is allocated as follows.

  3PM to 5PM on Feb 27th

Thanks!
--
M. Kudo

-----Original Message-----
From: ??????CTJ? 
Sent: Thursday, January 30, 2020 7:55 AM
To: cip-dev at lists.cip-project.org
Subject: 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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-23-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 
3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910 
4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-30  7:35 ` Chris Paterson
@ 2020-01-30  8:05   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-30  8:05 UTC (permalink / raw)
  To: cip-dev

Chris-san,

Thanks for letting us know your status.
Then, see you next week!

Best regards,
--
M. Kudo

-----Original Message-----
From: Chris Paterson <Chris.Paterson2@renesas.com> 
Sent: Thursday, January 30, 2020 4:36 PM
To: ??????CTJ? <masashi.kudo@cybertrust.co.jp>; cip-dev at lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hello Kudo-san, all,

> From: cip-dev <cip-dev-bounces@lists.cip-project.org> On Behalf Of 
> masashi.kudo at cybertrust.co.jp
> Sent: 29 January 2020 22:55
> 
> Hi all,
> 
> Kindly be reminded to attend the weekly meeting through IRC to discuss 
> technical topics with CIP kernel today.

Sorry for not joining in with last week's meeting. I was online, but Matrix was playing up and no messages were getting through.
Please accept my apologies for this week's meeting. I'm on annual leave 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=
> 136&p5=37&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-23-
> 09.00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 2. 
> Document a process on how to add tests to the CIP test setup - 
> patersonc

No progress from me.

> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910 4. Add 
> config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - 
> Iwamatsu-san
> 
> * Kernel maintenance updates
> * Kernel testing

Not much to report this week:
* I switched the remote PDUs in the Renesas LAVA lab with new (hopefully) reliable ones. This should improve uptime.
* In the last week for cip we've tested the 4.19.98-cip19 release, and the latest commits to the 4.4 and 4.19 branches.
  * https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines
* In the last week for linux-stable we've built/tested 4.4.211, 4.4.212, 4.19.99, 4.19.100 and many variants of the release candidates.
  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.4.y
  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.19.y

Kind regards, Chris

> * CIP Core
> * Software update
> * 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.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-29 22:54 masashi.kudo at cybertrust.co.jp
@ 2020-01-30  7:35 ` Chris Paterson
  2020-01-30  8:05   ` masashi.kudo at cybertrust.co.jp
  2020-01-30 13:29 ` masashi.kudo at cybertrust.co.jp
  1 sibling, 1 reply; 195+ messages in thread
From: Chris Paterson @ 2020-01-30  7:35 UTC (permalink / raw)
  To: cip-dev

Hello Kudo-san, all,

> From: cip-dev <cip-dev-bounces@lists.cip-project.org> On Behalf Of
> masashi.kudo at cybertrust.co.jp
> Sent: 29 January 2020 22:55
> 
> Hi all,
> 
> Kindly be reminded to attend the weekly meeting through IRC to discuss
> technical topics with CIP kernel today.

Sorry for not joining in with last week's meeting. I was online, but Matrix was playing up and no messages were getting through.
Please accept my apologies for this week's meeting. I'm on annual leave 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=
> 136&p5=37&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-23-
> 09.00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san
> 2. Document a process on how to add tests to the CIP test setup - patersonc

No progress from me.

> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
> 4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  -
> Iwamatsu-san
> 
> * Kernel maintenance updates
> * Kernel testing

Not much to report this week:
* I switched the remote PDUs in the Renesas LAVA lab with new (hopefully) reliable ones. This should improve uptime.
* In the last week for cip we've tested the 4.19.98-cip19 release, and the latest commits to the 4.4 and 4.19 branches.
  * https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines
* In the last week for linux-stable we've built/tested 4.4.211, 4.4.212, 4.19.99, 4.19.100 and many variants of the release candidates.
  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.4.y
  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.19.y

Kind regards, Chris

> * CIP Core
> * Software update
> * 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.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-01-29 22:54 masashi.kudo at cybertrust.co.jp
  2020-01-30  7:35 ` Chris Paterson
  2020-01-30 13:29 ` masashi.kudo at cybertrust.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-29 22:54 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-23-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 
3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-23  8:33 ` Chen-Yu Tsai
@ 2020-01-23  8:35   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-23  8:35 UTC (permalink / raw)
  To: cip-dev

Hi, Chen-Yu san,

Thanks for sharing your status!
Then, see you next week!

Best regards,
--
M. Kudo

-----Original Message-----
From: Chen-Yu Tsai <wens@kernel.org> 
Sent: Thursday, January 23, 2020 5:34 PM
To: ??????CTJ? <masashi.kudo@cybertrust.co.jp>
Cc: cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi,

On Thu, Jan 23, 2020 at 6:55 AM <masashi.kudo@cybertrust.co.jp> wrote:
>
> 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=2019&m
> onth=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6
> =248
>
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
>
> Channel:
> * irc:chat.freenode.net:6667/cip
>
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00
> .log.html
>
> Agenda:
>
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 2. 
> Document a process on how to add tests to the CIP test setup - 
> patersonc 3. Arrangement of F2F Kernel Meeting in Nuremberg - 
> masashi910 4. Add config for BBB to both 4.4 and 4.19 (done for 
> qemux86-64)  - Iwamatsu-san
>
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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.

I won't be attending today's meeting.

Nothing much on my end. I reviewed a couple merge requests from Ben regarding CVEs. Three of the new ones are resolved; the last is related to ashmem in staging which is probably only used with Android.

There are some data updates to classify-failed-patches that I haven't pushed out. Nothing looks critical this week.

Regards
ChenYu

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-22 22:55 masashi.kudo at cybertrust.co.jp
@ 2020-01-23  8:33 ` Chen-Yu Tsai
  2020-01-23  8:35   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: Chen-Yu Tsai @ 2020-01-23  8:33 UTC (permalink / raw)
  To: cip-dev

Hi,

On Thu, Jan 23, 2020 at 6:55 AM <masashi.kudo@cybertrust.co.jp> wrote:
>
> 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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
>
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
>
> Channel:
> * irc:chat.freenode.net:6667/cip
>
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00.log.html
>
> Agenda:
>
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san
> 2. Document a process on how to add tests to the CIP test setup - patersonc
> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
> 4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san
>
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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.

I won't be attending today's meeting.

Nothing much on my end. I reviewed a couple merge requests from Ben
regarding CVEs. Three of the new ones are resolved; the last is related
to ashmem in staging which is probably only used with Android.

There are some data updates to classify-failed-patches that I haven't
pushed out. Nothing looks critical this week.

Regards
ChenYu

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-01-22 22:55 masashi.kudo at cybertrust.co.jp
  2020-01-23  8:33 ` Chen-Yu Tsai
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-22 22:55 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 
3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
4. Add config for BBB to both 4.4 and 4.19 (done for qemux86-64)  - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2020-01-15 23:16 masashi.kudo at cybertrust.co.jp
@ 2020-01-16  8:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2020-01-16  8:53 UTC (permalink / raw)
  To: cip-dev

Hi,

I cannot attend the IRC meeting today.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf
> Of masashi.kudo at cybertrust.co.jp
> Sent: Thursday, January 16, 2020 8:16 AM
> To: cip-dev at 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=3
> 7&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-09-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 

I tested on LAVA. But not finished.
  https://lava.ciplatform.org/scheduler/job/9499


> 2. Document a process on how to add tests to the CIP test setup - patersonc
> 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
> 4. Add config for qemux86-64 and BBB to both 4.4 and 4.19 - Iwamatsu-san

Qemux86-64's config already merged to cip-kernel-config.
BBB config is under testing. Please keep this A.I.

> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,

Best regards,
  Nobuhiro

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-01-15 23:16 masashi.kudo at cybertrust.co.jp
  2020-01-16  8:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-15 23:16 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-09-09.00.log.html

Agenda:

* Action item
1. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
2. Document a process on how to add tests to the CIP test setup - patersonc 
3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910
4. Add config for qemux86-64 and BBB to both 4.4 and 4.19 - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2020-01-09  0:56 masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2020-01-09  0:56 UTC (permalink / raw)
  To: cip-dev

Hi all,

A Happy New Year!
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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-26-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 
2. Create a way/process to run LTP only for release tests - patersonc 
3. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
4. Document a process on how to add tests to the CIP test setup - patersonc 
5. Arrangement of F2F Kernel Meeting in Nurnberg - masashi910
6. Add config for qemux86-64 and BBB to both 4.4 and 4.19 - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-12-25 22:52 masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-25 22:52 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-19-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 
2. Create a way/process to run LTP only for release tests - patersonc 
3. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
4. Document a process on how to add tests to the CIP test setup - patersonc 
5. Arrangement of F2F Kernel Meeting in Nurnberg - masashi910
6. Add config for qemux86-64 and BBB to both 4.4 and 4.19 -iwamatsu

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. IRC meeting next week
I would like to skip an IRC meeting next week. The next IRC meeting should be on January 9th.

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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-12-18 23:39 masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-18 23:39 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-12-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc
2. Create a way/process to run LTP only for release tests - patersonc
3. Combine rootfilesystem with kselftest binary - Iwamatsu-san
4. Document a process on how to add tests to the CIP test setup - patersonc
5. Arrangement of F2F Kernel Meeting in Nurnberg - masashi910

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. IRC meeting next week
I would like to hold an IRC meeting next week as well although it is a holiday season. I would like to double-check whether it is ok.

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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-12-12  9:50 ` masashi.kudo at cybertrust.co.jp
@ 2019-12-12 12:56   ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-12 12:56 UTC (permalink / raw)
  To: cip-dev

Hello, again,

Regarding the due date for the poll, 
in order to meet Kobayashi-san's request, please finish by Dec 18th instead of Jan 5.

Best regards,
--
M. Kudo

-----Original Message-----
From: ??????CTJ? 
Sent: Thursday, December 12, 2019 6:50 PM
To: cip-dev at lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi all, 

Regarding the following:
> 1. Proposed move from Mailman to Groups.io and kernel.org 2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll

I created a doodle poll as follows.
https://doodle.com/poll/73if9scwqrh5ge38

By compiling your opinions, I would like to propose our preferable slots at the next TSC (Jan 6 or 7). So, if you can respond to it by Jan 5, that would be appreciated.

Thanks,
--
M. Kudo

-----Original Message-----
From: ??????CTJ? 
Sent: Thursday, December 12, 2019 9:59 AM
To: cip-dev at lists.cip-project.org
Subject: 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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-05-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 2. Create a way/process to run LTP only for release tests - patersonc 3. Combine rootfilesystem with kselftest binary - Iwamatsu-san 4. Document a process on how to add tests to the CIP test setup - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Proposed move from Mailman to Groups.io and kernel.org 2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll

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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-12-12  0:59 masashi.kudo at cybertrust.co.jp
  2019-12-12  7:04 ` nobuhiro1.iwamatsu at toshiba.co.jp
@ 2019-12-12  9:50 ` masashi.kudo at cybertrust.co.jp
  2019-12-12 12:56   ` masashi.kudo at cybertrust.co.jp
  1 sibling, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-12  9:50 UTC (permalink / raw)
  To: cip-dev

Hi all, 

Regarding the following:
> 1. Proposed move from Mailman to Groups.io and kernel.org 2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll

I created a doodle poll as follows.
https://doodle.com/poll/73if9scwqrh5ge38

By compiling your opinions, I would like to propose our preferable slots at the next TSC (Jan 6 or 7). So, if you can respond to it by Jan 5, that would be appreciated.

Thanks,
--
M. Kudo

-----Original Message-----
From: ??????CTJ? 
Sent: Thursday, December 12, 2019 9:59 AM
To: cip-dev at lists.cip-project.org
Subject: 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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-05-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 2. Create a way/process to run LTP only for release tests - patersonc 3. Combine rootfilesystem with kselftest binary - Iwamatsu-san 4. Document a process on how to add tests to the CIP test setup - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Proposed move from Mailman to Groups.io and kernel.org 2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll

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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-12-12  0:59 masashi.kudo at cybertrust.co.jp
@ 2019-12-12  7:04 ` nobuhiro1.iwamatsu at toshiba.co.jp
  2019-12-12  9:50 ` masashi.kudo at cybertrust.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2019-12-12  7:04 UTC (permalink / raw)
  To: cip-dev

Hi all,

I may not be able to join the meeting.
I add my update to this mail.

> -----Original Message-----
> From: cip-dev [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf
> Of masashi.kudo at cybertrust.co.jp
> Sent: Thursday, December 12, 2019 9:59 AM
> To: cip-dev at 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=2019
> &month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=3
> 7&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-05-09.
> 00.log.html
> 
> Agenda:
> 
> * Action item
> 1. Test LTS (pre)releases directly - patersonc 2. Create a way/process
> to run LTP only for release tests - patersonc 3. Combine rootfilesystem
> with kselftest binary - Iwamatsu-san 4. Document a process on how to add
> tests to the CIP test setup - patersonc
> 

No 4 does not update.

> * Kernel maintenance updates

I reviewed 4.4.202, and stable-rc on stable ML.
I send some comments for 4.19.y and other.

Best regards,
  Nobuhiro

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-12-12  0:59 masashi.kudo at cybertrust.co.jp
  2019-12-12  7:04 ` nobuhiro1.iwamatsu at toshiba.co.jp
  2019-12-12  9:50 ` masashi.kudo at cybertrust.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-12  0:59 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-05-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc
2. Create a way/process to run LTP only for release tests - patersonc
3. Combine rootfilesystem with kselftest binary - Iwamatsu-san
4. Document a process on how to add tests to the CIP test setup - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* AOB
1. Proposed move from Mailman to Groups.io and kernel.org
2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll

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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-12-05  0:28 masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-12-05  0:28 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. 
I, Masashi Kudo (IRC ID: masashi910), will chair meetings starting today by taking over SZ-san's role.

*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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-28-09.00.log.html

Agenda:
* Action item
1. Test LTS (pre)releases directly - patersonc
2. Create a way/process to run LTP only for release tests - patersonc
3. Combine rootfilesystem with kselftest binary - Iwamatsu-san
4. Document a process on how to add tests to the CIP test setup - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-11-28  1:51 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-11-28  1:51 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=28&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
          
US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-21-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 

2. Create a way/process to run LTP only for release tests - patersonc 

3. Combine rootfilesystem with kselftest binary - Iwamatsu-san 

4. Document a process on how to add tests to the CIP test setup - patersonc 

5. Split out non-Kernel config sections from gitlab-ci.yml - patersonc

6. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team 

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-11-21  0:30 SZ Lin (林上智)
  2019-11-21  7:38 ` Nobuhiro Iwamatsu
@ 2019-11-21  8:53 ` Chris Paterson
  1 sibling, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2019-11-21  8:53 UTC (permalink / raw)
  To: cip-dev

Hello SZ,

> From: cip-dev <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (???)
> Sent: 21 November 2019 00:30
> 
> 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=2019&m
> onth=11&day=21&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p
> 5=37&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-14-
> 09.00.log.html
> 
> Agenda:
> 
> * Action item

To save some time during the meeting, here is the latest status from me...

> 1. Test LTS (pre)releases directly - patersonc
Everything is working and we've found a few issues that have been reported to stable.
Remaining tasks are:
* Add a way to identify in GitLab what commit is being tested.
* Move everything from cip-playground to cip-project/cip-testing.

> 2. Ask KernelCI for recommendations on what tests to run - patersonc
I can't remember the background behind this, but I think we have a long enough list of tests to support for now.
I think we can close this.

> 3. Create a way/process to run LTP only for release tests - patersonc
Technically this is now possible due to updates to linux-cip-ci.
We just need to decide the best method to define 'release' testing.
I'll propose a method of how to do this to the maintainers soon.

> 4. Combine rootfilesystem with kselftest binary - Iwamatsu-san
> 5. Document a process on how to add tests to the CIP test setup - patersonc
No updates.

> 6. Split out non-Kernel config sections from gitlab-ci.yml - patersonc
Prototype complete. I just need to move from cip-playground to cip-testing.
https://gitlab.com/patersonc/linux-cip-pipelines/tree/initial-work
https://gitlab.com/cip-project/cip-kernel/linux-cip/blob/ci/patersonc/linux-4.19.y-cip/.gitlab-ci.yml

Kind regards, Chris

> 7. Do we want to go with the current approach where GitLab CI is run ?out of
> tree?- Kernel team
> 8. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-11-21  0:30 SZ Lin (林上智)
@ 2019-11-21  7:38 ` Nobuhiro Iwamatsu
  2019-11-21  8:53 ` Chris Paterson
  1 sibling, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2019-11-21  7:38 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

I can't participate IRC meeting today.

2019?11?21?(?) 9:45 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> 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=2019&month=11&day=21&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
>
> US-West US-East   UK     DE     TW     JP
> 01:00    04:00   09:00   10:00   17:00   18:00
>
> Channel:
> * irc:chat.freenode.net:6667/cip
>
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-14-09.00.log.html
>
> Agenda:
>
> * Action item
> 1. Test LTS (pre)releases directly - patersonc
> 2. Ask KernelCI for recommendations on what tests to run - patersonc
> 3. Create a way/process to run LTP only for release tests - patersonc
> 4. Combine rootfilesystem with kselftest binary - Iwamatsu-san

I am working yet. please keep this A.I.

> 5. Document a process on how to add tests to the CIP test setup - patersonc
> 6. Split out non-Kernel config sections from gitlab-ci.yml - patersonc
> 7. Do we want to go with the current approach where GitLab CI is run ?out of tree?- Kernel team
> 8. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team
>
> * Kernel maintenance updates

I reviewed v4.4.201, 202-rc and v4.19.85-rc.

> * Kernel testing
> * CIP Core
> * Software update
> * 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

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-11-21  0:30 SZ Lin (林上智)
  2019-11-21  7:38 ` Nobuhiro Iwamatsu
  2019-11-21  8:53 ` Chris Paterson
  0 siblings, 2 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-11-21  0:30 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=21&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
          
US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-14-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 
2. Ask KernelCI for recommendations on what tests to run - patersonc 
3. Create a way/process to run LTP only for release tests - patersonc 
4. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
5. Document a process on how to add tests to the CIP test setup - patersonc 
6. Split out non-Kernel config sections from gitlab-ci.yml - patersonc 
7. Do we want to go with the current approach where GitLab CI is run ?out of tree?- Kernel team 
8. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team 

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-11-14  1:41 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-11-14  1:41 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=14&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
          
US-West US-East   UK     DE     TW     JP
01:00    04:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/11/cip.2019-11-07-09.00.log.html

Agenda:

* Action item
1. Test LTS (pre)releases directly - patersonc 
2. Ask KernelCI for recommendations on what tests to run - patersonc 
3. Create a way/process to run LTP only for release tests - patersonc 
4. Investigate the RT test tools - Pavel 
5. Combine rootfilesystem with kselftest binary - Iwamatsu-san 
6. Document a process on how to add tests to the CIP test setup - patersonc 
7. Split out non-Kernel config sections from gitlab-ci.yml - patersonc 
8. Do we want to go with the current approach where GitLab CI is run ?out of tree?- Kernel team
9. Ask RT admin to put CIP RT kernel to their CI-RT - Kernel team
10. Provide the CIP mini-summit slide with as a PDF file - Pavel

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-11-07  7:15 ` nobuhiro1.iwamatsu at toshiba.co.jp
@ 2019-11-07  9:17   ` SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-11-07  9:17 UTC (permalink / raw)
  To: cip-dev

Hi Iwamatsu-san,

> From: nobuhiro1.iwamatsu at toshiba.co.jp
> 
> Hi SZ,
> 
> I may be late or unable to join meeting.

Thank you for your heads up, I've listed your comments in the IRC meeting.

SZ

> 
> > * Action item
> > 1. Provide the cases to cip-testing to build up the test environment -
> > Iwamatsu-san
> Merged by Chris. Please close this A.I. Thanks for Chris.
>    https://gitlab.com/cip-project/cip-testing/linux-cip-ci/merge_requests/24
> 
> > 2. Test LTS (pre)releases directly - patersonc 3. Ask KernelCI for
> > recommendations on what tests to run - patersonc 4. Create a
> > way/process to run LTP only for release tests - patersonc 5.
> > Investigate the RT test tools - Pavel 6. Combine rootfilesystem with
> > kselftest binary - Iwamatsu-san
> 
> This is WIP. Please keep.
> 
> > 7. Document a process on how to add tests to the CIP test setup -
> > patersonc 8. Split out non-Kernel config sections from gitlab-ci.yml -
> > patersonc 9. Do we want to go with the current approach where GitLab
> > CI is run ?out of tree?- Kernel team
> We discussion by Mail now. Some opinions come from Chris.
> 
> > * Kernel maintenance updates
> I reviewed v4.4.198.
> 
> Best regards,
>   Nobuhiro
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org
> > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (?
> > ??)
> > Sent: Thursday, November 7, 2019 10:56 AM
> > To: cip-dev at 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=2019
> >
> &month=11&day=7&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=1
> 36&p5=37
> > &p6=248
> >
> > US-West US-East?? UK???? DE???? TW???? JP
> > 01:00??? 04:00?? 09:00?? 10:00?? 17:00?? 18:00
> >
> > Channel:
> > * irc:chat.freenode.net:6667/cip
> >
> > Last week's meeting minutes:
> > https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-24-09.
> > 00.html
> >
> > Agenda:
> >
> > * Action item
> > 1. Provide the cases to cip-testing to build up the test environment -
> > Iwamatsu-san 2. Test LTS (pre)releases directly - patersonc 3. Ask
> > KernelCI for recommendations on what tests to run - patersonc 4.
> > Create a way/process to run LTP only for release tests - patersonc 5.
> > Investigate the RT test tools - Pavel 6. Combine rootfilesystem with
> > kselftest binary
> > - Iwamatsu-san 7. Document a process on how to add tests to the CIP
> > test setup - patersonc 8. Split out non-Kernel config sections from
> > gitlab-ci.yml - patersonc 9. Do we want to go with the current
> > approach where GitLab CI is run ?out of tree?- Kernel team
> >
> > * Kernel maintenance updates
> > * Kernel testing
> > * CIP Core
> > * Software update
> > * 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,
> >
> > SZ Lin, Moxa.
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-11-07  1:56 SZ Lin (林上智)
@ 2019-11-07  7:15 ` nobuhiro1.iwamatsu at toshiba.co.jp
  2019-11-07  9:17   ` SZ Lin (林上智)
  0 siblings, 1 reply; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2019-11-07  7:15 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

I may be late or unable to join meeting.

> * Action item
> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 
Merged by Chris. Please close this A.I. Thanks for Chris.
   https://gitlab.com/cip-project/cip-testing/linux-cip-ci/merge_requests/24

> 2. Test LTS (pre)releases directly - patersonc 
> 3. Ask KernelCI for recommendations on what tests to run - patersonc 
> 4. Create a way/process to run LTP only for release tests - patersonc
> 5. Investigate the RT test tools - Pavel 6. Combine rootfilesystem with kselftest binary - Iwamatsu-san

This is WIP. Please keep.

> 7. Document a process on how to add tests to the CIP test setup - patersonc
> 8. Split out non-Kernel config sections from gitlab-ci.yml - patersonc
> 9. Do we want to go with the current approach where GitLab CI is run ?out of tree?- Kernel team
We discussion by Mail now. Some opinions come from Chris.

> * Kernel maintenance updates
I reviewed v4.4.198.

Best regards,
  Nobuhiro

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, November 7, 2019 10:56 AM
> To: cip-dev at 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=2019
> &month=11&day=7&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37
> &p6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 01:00??? 04:00?? 09:00?? 10:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Last week's meeting minutes:
> https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-24-09.
> 00.html
> 
> Agenda:
> 
> * Action item
> 1. Provide the cases to cip-testing to build up the test environment -
> Iwamatsu-san 2. Test LTS (pre)releases directly - patersonc 3. Ask
> KernelCI for recommendations on what tests to run - patersonc 4. Create
> a way/process to run LTP only for release tests - patersonc 5. Investigate
> the RT test tools - Pavel 6. Combine rootfilesystem with kselftest binary
> - Iwamatsu-san 7. Document a process on how to add tests to the CIP test
> setup - patersonc 8. Split out non-Kernel config sections from
> gitlab-ci.yml - patersonc 9. Do we want to go with the current approach
> where GitLab CI is run ?out of tree?- Kernel team
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-11-07  1:56 SZ Lin (林上智)
  2019-11-07  7:15 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-11-07  1:56 UTC (permalink / raw)
  To: cip-dev

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=2019&month=11&day=7&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
????????? 
US-West US-East?? UK???? DE???? TW???? JP
01:00??? 04:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-24-09.00.html

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 
2. Test LTS (pre)releases directly - patersonc
3. Ask KernelCI for recommendations on what tests to run - patersonc
4. Create a way/process to run LTP only for release tests - patersonc
5. Investigate the RT test tools - Pavel
6. Combine rootfilesystem with kselftest binary - Iwamatsu-san
7. Document a process on how to add tests to the CIP test setup - patersonc
8. Split out non-Kernel config sections from gitlab-ci.yml - patersonc
9. Do we want to go with the current approach where GitLab CI is run ?out of tree?- Kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-10-24  5:53   ` SZ Lin (林上智)
@ 2019-10-24  6:01     ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-10-24  6:01 UTC (permalink / raw)
  To: cip-dev

Hi, SZ-san,

Yes, please close this AI. Thanks very much for your cooperation.

Best regards,
--
M. Kudo

From: SZ Lin (???) <SZ.Lin@moxa.com>
Sent: Thursday, October 24, 2019 2:54 PM
To: ??????CTJ? <masashi.kudo@cybertrust.co.jp>
Cc: cip-dev at lists.cip-project.org
Subject: RE: [cip-dev] CIP IRC weekly meeting today

Hi Kudo-san,

Thanks for you heads up.

For now, we?re waiting for your patches. So I think we can close this AI if you have no objection.

SZ

From: masashi.kudo@cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp> <masashi.kudo at cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp>>
Sent: Thursday, October 24, 2019 1:51 PM
To: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Cc: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] CIP IRC weekly meeting today

SZ-san,

> 3. Review the proposal from Kudo-san - Kernel team

I'm sorry, but I cannot attend today's meeting due to another appointment.
If I need to do anything, please let me know.

Best regards,
--
M. Kudo

2019?10?24?(?) 10:55 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:

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=2019&month=10&day=24&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>



Last week's meeting minutes:

https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-17-09.00.html



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Test LTS (pre)releases directly ? patersonc



3. Review the proposal from Kudo-san - Kernel team



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191024/694621cd/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-10-24  5:50 ` masashi.kudo at cybertrust.co.jp
@ 2019-10-24  5:53   ` SZ Lin (林上智)
  2019-10-24  6:01     ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-10-24  5:53 UTC (permalink / raw)
  To: cip-dev

Hi Kudo-san,

Thanks for you heads up.

For now, we?re waiting for your patches. So I think we can close this AI if you have no objection.

SZ

From: masashi.kudo@cybertrust.co.jp <masashi.kudo@cybertrust.co.jp>
Sent: Thursday, October 24, 2019 1:51 PM
To: SZ Lin (???) <SZ.Lin@moxa.com>
Cc: cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

SZ-san,

> 3. Review the proposal from Kudo-san - Kernel team

I'm sorry, but I cannot attend today's meeting due to another appointment.
If I need to do anything, please let me know.

Best regards,
--
M. Kudo

2019?10?24?(?) 10:55 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:

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=2019&month=10&day=24&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>



Last week's meeting minutes:

https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-17-09.00.html



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Test LTS (pre)releases directly ? patersonc



3. Review the proposal from Kudo-san - Kernel team



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191024/fe1f0cc6/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-10-24  1:55 SZ Lin (林上智)
@ 2019-10-24  5:50 ` masashi.kudo at cybertrust.co.jp
  2019-10-24  5:53   ` SZ Lin (林上智)
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-10-24  5:50 UTC (permalink / raw)
  To: cip-dev

SZ-san,

> 3. Review the proposal from Kudo-san - Kernel team

I'm sorry, but I cannot attend today's meeting due to another appointment.
If I need to do anything, please let me know.

Best regards,
--
M. Kudo

2019?10?24?(?) 10:55 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:

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=2019&month=10&day=24&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>



Last week's meeting minutes:

https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-17-09.00.html



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Test LTS (pre)releases directly ? patersonc



3. Review the proposal from Kudo-san - Kernel team



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191024/e25d8ecc/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-10-24  1:55 SZ Lin (林上智)
  2019-10-24  5:50 ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-10-24  1:55 UTC (permalink / raw)
  To: cip-dev

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=2019&month=10&day=24&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Last week's meeting minutes:

https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-17-09.00.html



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Test LTS (pre)releases directly ? patersonc



3. Review the proposal from Kudo-san - Kernel team



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191024/1f5cac32/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-10-17  2:05 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-10-17  2:05 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=10&day=17&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
????????? 
US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last week's meeting minutes:
https://irclogs.baserock.org/meetings/cip/2019/10/cip.2019-10-10-09.00.html

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Test LTS (pre)releases directly ? patersonc

3. Review the proposal from Kudo-san - Kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-10-10  2:32 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-10-10  2:32 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=10&day=10&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Test LTS (pre)releases directly ? patersonc



3. Review the proposal from Kudo-san - Kernel team



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191010/737b0714/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-10-03  1:56 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-10-03  1:56 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=10&day=3&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
          
US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Test LTS (pre)releases directly ? patersonc

3. Move cip-core repo to cip-project/cip-core - kazu

4. Review the proposal from Kudo-san - Kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-09-26  3:01   ` masashi.kudo at cybertrust.co.jp
  2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
@ 2019-10-01  2:47     ` masashi.kudo at cybertrust.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-10-01  2:47 UTC (permalink / raw)
  To: cip-dev

Hi, Pavel-san,

At the CIP kernel meeting, there was the following conversation regarding the Cybertrust proposal.
(BTW, 'masashi910' is me. )

[18:43] <pave1> masashi910: We don't need working version at the moment. But if you could mail the patches, or post pointer for them, or at least diffstat... That would help.
[18:44] <masashi910> pavel: Thanks. Our work is currently being done locally. I will discuss our team how to share the patches with you.

The current work which contains all CIP kernel files is compiled into a tar ball, and I uploaded the ball under the following repository.
https://github.com/masashi910/tmp-cip-xilinx-mpsoc/

Please let me reiterate the following:
 - Cybertrust so far identified patches (in BSP) to be applied to CIP SLTS4.19 for some use cases
 - Those patches were from BSP, and our next step is to figure out which patches are actually in Mainline tree.
 - In another word, some of the current identified patches may not be in Mainline tree, yet.

If you have any questions, please let me know.

Best regards,
--
M. Kudo

2019?9?26?(?) 12:01 <masashi.kudo at cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp>>:
Hi, SZ-san, All,

Cybertrust would like to propose some contribution as described in the attached material.
I would appreciate it if this topic can be discussed in AOB.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

---------- Forwarded message ---------
From: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Date: 2019?9?26?(?) 11:46
Subject: [cip-dev] CIP IRC weekly meeting today
To: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>>


Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=26&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Test LTS (pre)releases directly - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191001/c9da90b5/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
@ 2019-09-30  7:19       ` Chris Paterson
  0 siblings, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2019-09-30  7:19 UTC (permalink / raw)
  To: cip-dev

Hello Kudo-san,

Thank you for the information.

Kind regards, Chris

From: cip-dev-bounces@lists.cip-project.org <cip-dev-bounces@lists.cip-project.org> On Behalf Of masashi.kudo at cybertrust.co.jp
Sent: 28 September 2019 05:30
To: masashi.kudo at cybertrust.co.jp
Cc: SZ.Lin at moxa.com; cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Chris-san,

At the CIP kernel meeting, there was the following conversation regarding the Cybertrust proposal.
(BTW, 'masashi910' is me. )

[18:45] <patersonc> masashi910: Are you planning to set up your own LAVA worker?
[18:45] <masashi910> patersonc: Let me check. I will get back to you by email.

Cybertrust plans to set up our own LAVA worker in our Lab.
If you have comments or concerns, please let me know.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

2019?9?26?(?) 12:01 <masashi.kudo at cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp>>:
Hi, SZ-san, All,

Cybertrust would like to propose some contribution as described in the attached material.
I would appreciate it if this topic can be discussed in AOB.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

---------- Forwarded message ---------
From: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Date: 2019?9?26?(?) 11:46
Subject: [cip-dev] CIP IRC weekly meeting today
To: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>>


Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=26&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Test LTS (pre)releases directly - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190930/060a6cdb/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-09-26  3:01   ` masashi.kudo at cybertrust.co.jp
@ 2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
  2019-09-30  7:19       ` Chris Paterson
  2019-10-01  2:47     ` masashi.kudo at cybertrust.co.jp
  1 sibling, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-09-28  4:30 UTC (permalink / raw)
  To: cip-dev

Chris-san,

At the CIP kernel meeting, there was the following conversation regarding the Cybertrust proposal.
(BTW, 'masashi910' is me. )

[18:45] <patersonc> masashi910: Are you planning to set up your own LAVA worker?
[18:45] <masashi910> patersonc: Let me check. I will get back to you by email.

Cybertrust plans to set up our own LAVA worker in our Lab.
If you have comments or concerns, please let me know.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

2019?9?26?(?) 12:01 <masashi.kudo at cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp>>:
Hi, SZ-san, All,

Cybertrust would like to propose some contribution as described in the attached material.
I would appreciate it if this topic can be discussed in AOB.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

---------- Forwarded message ---------
From: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Date: 2019?9?26?(?) 11:46
Subject: [cip-dev] CIP IRC weekly meeting today
To: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>>


Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=26&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Test LTS (pre)releases directly - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190928/258178d6/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
       [not found] ` <CAFa_k0gBzv-2bOF_pGbpvZQyQ1ocEu-bsBNT_JsWi12cxrK-Pg@mail.gmail.com>
@ 2019-09-26  3:01   ` masashi.kudo at cybertrust.co.jp
  2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
  2019-10-01  2:47     ` masashi.kudo at cybertrust.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-09-26  3:01 UTC (permalink / raw)
  To: cip-dev

Hi, SZ-san, All,

Cybertrust would like to propose some contribution as described in the attached material.
I would appreciate it if this topic can be discussed in AOB.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

---------- Forwarded message ---------
From: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Date: 2019?9?26?(?) 11:46
Subject: [cip-dev] CIP IRC weekly meeting today
To: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org> <cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>>


Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=26&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Test LTS (pre)releases directly - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190926/19df8723/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: [public]ContributionProposal-CTJ.pdf
Type: application/pdf
Size: 295564 bytes
Desc: [public]ContributionProposal-CTJ.pdf
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190926/19df8723/attachment-0001.pdf>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-09-26  2:46 SZ Lin (林上智)
       [not found] ` <CAFa_k0gBzv-2bOF_pGbpvZQyQ1ocEu-bsBNT_JsWi12cxrK-Pg@mail.gmail.com>
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-09-26  2:46 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=26&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
          
US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Test LTS (pre)releases directly - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-09-19  1:27 SZ Lin (林上智)
@ 2019-09-19 11:08 ` Pavel Machek
  0 siblings, 0 replies; 195+ messages in thread
From: Pavel Machek @ 2019-09-19 11:08 UTC (permalink / raw)
  To: cip-dev

Hi!

> Kindly be reminded to attend the weekly meeting through IRC to
> discuss technical topics with CIP kernel today.

I'm sorry I did not make it to the meeting.

>From the last meeting, I reviewed most of 4.19.73 and 4.19.74.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190919/ff504481/attachment.sig>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-09-19  1:27 SZ Lin (林上智)
  2019-09-19 11:08 ` Pavel Machek
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-09-19  1:27 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=9&day=19&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
????????? 
US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Ask cip-dev which configurations need testing - patersonc 

3. Test LTS (pre)releases directly - patersonc

4. Invesgate gitlab mirror issue - szlin

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-09-12  1:37 SZ Lin (林上智)
@ 2019-09-12 22:46 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2019-09-12 22:46 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

I could not attend yesterday's IRC meeting because 
I was attended in another meeting.

> * Action item
> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

No update.

And I reviewed v4.4.166.

Best regards,
  Nobuhiro

From: cip-dev-bounces@lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (???)
Sent: Thursday, September 12, 2019 10:38 AM
To: cip-dev at 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 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=2019&month=9&day=12&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
????????? 
US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Ask cip-dev which configurations need testing - patersonc 

3. Test LTS (pre)releases directly ? patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-09-12  1:37 SZ Lin (林上智)
  2019-09-12 22:46 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-09-12  1:37 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=9&day=12&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Ask cip-dev which configurations need testing - patersonc



3. Test LTS (pre)releases directly ? patersonc



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,


SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190912/80273b68/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-09-05  1:34 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-09-05  1:34 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=9&day=5&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Action item

1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san



2. Ask cip-dev which configurations need testing - patersonc



3. Test LTS (pre)releases directly ? patersonc



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190905/56460d42/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-08-29  4:05   ` SZ Lin (林上智)
@ 2019-08-29  7:13     ` masashi.kudo at cybertrust.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-08-29  7:13 UTC (permalink / raw)
  To: cip-dev

SZ-san,

I am sorry, but it turned out that I need to withdraw my request for now.
Let me propose our idea some later time.
I am sorry to confuse you.

Best regards,
--
M. Kudo

2019?8?29?(?) 13:05 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:
Hi Kudo-san,

Noted, thank you for your heads up.

SZ

From: masashi.kudo@cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp> <masashi.kudo at cybertrust.co.jp<mailto:masashi.kudo@cybertrust.co.jp>>
Sent: Thursday, August 29, 2019 10:51 AM
To: SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>
Cc: cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hello, SZ-san, All,

Cybertrust has some proposal to the CIP kernel team.
I would appreciate it if you can add "Cybertrust Proposal" to the agenda.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

2019?8?29?(?) 10:31 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:
Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day29&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=24

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Ask cip-dev which configurations need testing - patersonc

3. Test LTS (pre)releases directly ? patersonc

4. Discuss and make a decision on default compiler's options - kernel team

5. Look for the new maintainer of CIP security tracker ? kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190829/ea87d6da/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-08-29  2:51 ` masashi.kudo at cybertrust.co.jp
@ 2019-08-29  4:05   ` SZ Lin (林上智)
  2019-08-29  7:13     ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-29  4:05 UTC (permalink / raw)
  To: cip-dev

Hi Kudo-san,

Noted, thank you for your heads up.

SZ

From: masashi.kudo@cybertrust.co.jp <masashi.kudo@cybertrust.co.jp>
Sent: Thursday, August 29, 2019 10:51 AM
To: SZ Lin (???) <SZ.Lin@moxa.com>
Cc: cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hello, SZ-san, All,

Cybertrust has some proposal to the CIP kernel team.
I would appreciate it if you can add "Cybertrust Proposal" to the agenda.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

2019?8?29?(?) 10:31 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:
Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day29&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=24

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Ask cip-dev which configurations need testing - patersonc

3. Test LTS (pre)releases directly ? patersonc

4. Discuss and make a decision on default compiler's options - kernel team

5. Look for the new maintainer of CIP security tracker ? kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190829/7ffec5c6/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-08-29  1:31 SZ Lin (林上智)
@ 2019-08-29  2:51 ` masashi.kudo at cybertrust.co.jp
  2019-08-29  4:05   ` SZ Lin (林上智)
  0 siblings, 1 reply; 195+ messages in thread
From: masashi.kudo at cybertrust.co.jp @ 2019-08-29  2:51 UTC (permalink / raw)
  To: cip-dev

Hello, SZ-san, All,

Cybertrust has some proposal to the CIP kernel team.
I would appreciate it if you can add "Cybertrust Proposal" to the agenda.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

2019?8?29?(?) 10:31 SZ Lin (???) <SZ.Lin at moxa.com<mailto:SZ.Lin@moxa.com>>:
Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day29&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=24

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip<http://chat.freenode.net:6667/cip>

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san

2. Ask cip-dev which configurations need testing - patersonc

3. Test LTS (pre)releases directly ? patersonc

4. Discuss and make a decision on default compiler's options - kernel team

5. Look for the new maintainer of CIP security tracker ? kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190829/a288a0f2/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-08-29  1:31 SZ Lin (林上智)
  2019-08-29  2:51 ` masashi.kudo at cybertrust.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-29  1:31 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day29&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=24
	
US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 

2. Ask cip-dev which configurations need testing - patersonc 

3. Test LTS (pre)releases directly ? patersonc

4. Discuss and make a decision on default compiler's options - kernel team

5. Look for the new maintainer of CIP security tracker ? kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-08-22  1:31 SZ Lin (林上智)
@ 2019-08-22 20:35 ` Pavel Machek
  0 siblings, 0 replies; 195+ messages in thread
From: Pavel Machek @ 2019-08-22 20:35 UTC (permalink / raw)
  To: cip-dev

Hi!

> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 
> *Please note that 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=2019&month=8&day22&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248
> 
> US-West US-East   UK     DE     TW     JP
> 02:00    05:00   10:00   11:00   17:00   18:00

I got carried away with other project, and forgot about time. Sorry
about that.

>From last meeting, I reviewed v4.19.67 and started reviewing v4.19.68.

Best regards,
									Pavel
										
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190822/10d8a8ae/attachment.sig>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-08-22  1:31 SZ Lin (林上智)
  2019-08-22 20:35 ` Pavel Machek
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-22  1:31 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day22&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san 
2. Ask cip-dev which configurations need testing - patersonc 
3. Test LTS (pre)releases directly - patersonc 
4. Discuss the primary repository in CIP kernel development (kernel.org or gitlab) - kernel team 
5. Discuss and make a decision on default compiler's options - kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-08-15  1:04 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-15  1:04 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day15&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
2. Ask cip-dev which configurations need testing - patersonc
3. Test LTS (pre)releases directly - patersonc
4. Discuss the primary repository in CIP kernel development (kernel.org or gitlab) - kernel team
5. Discuss and make a decision on default compiler's options - kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

I won't be able to attend this meeting, Gavin will chair today's meeting.

Best regards,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-08-08  1:55 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-08  1:55 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day8&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item

1. Work out a solution for LAVA master backups - patersonc
2. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
3. Ask cip-dev which configurations need testing - patersonc
4. Confirm we can enable high-res timers for every board - pavel
5. Add support for PowerPC (4.4 Toshiba config) - patersonc
6. Test LTS (pre)releases directly - patersonc
7. Discuss the primary repository in CIP kernel development (kernel.org or gitlab) - kernel team
8. Review and merge "gitlab-ci.yml" - pavel

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-08-01  1:03 SZ Lin (林上智)
@ 2019-08-01  8:05 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2019-08-01  8:05 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

I can not participate IRC meeting for personal reasons.

Best regards,
  Nobuhiro


> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, August 1, 2019 10:03 AM
> To: cip-dev at 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 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=2019
> &month=8&day1&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p
> 6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * Action item
> 1. Provide the script for CIP kernel config collection - bwh #link
> https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.htm
> l
> 2. Work out a solution for LAVA master backups - patersonc 3. Provide
> the cases to cip-testing to build up the test environment - Iwamatsu-san
> 4. Ask cip-dev which configurations need testing - Chris 5. Confirm we
> can enable high-res timers for every board - Pavel 6. Add support for
> PowerPC (4.4 Toshiba config) - Chris 7. Test LTS (pre)releases directly
> - Chris 8. Discuss the primary repository in CIP kernel development
> (kernel.org or gitlab) - kernel team
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-08-01  1:03 SZ Lin (林上智)
  2019-08-01  8:05 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-08-01  1:03 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=8&day1&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the script for CIP kernel config collection - bwh 
#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html
2. Work out a solution for LAVA master backups - patersonc 
3. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
4. Ask cip-dev which configurations need testing - Chris
5. Confirm we can enable high-res timers for every board - Pavel
6. Add support for PowerPC (4.4 Toshiba config) - Chris
7. Test LTS (pre)releases directly - Chris
8. Discuss the primary repository in CIP kernel development (kernel.org or gitlab) - kernel team

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-07-25  1:06 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-07-25  1:06 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=7&day25&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the script for CIP kernel config collection - bwh 
#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html
2. Try updating CIP RT kernel to 4.19.50 - Pavel 
#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html
3. Fix release number in CIP RT kernel - pavel
4. Work out a solution for LAVA master backups - patersonc
5. Review "gitlab-ci.yml" patches before OSS-J - pavel
* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-07-11  2:25 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-07-11  2:25 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=7&day11&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Action item

1. Provide the script for CIP kernel config collection - bwh

#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html

2. List real time kernel questions to ask Daniel Wagner - szlin

3. Try updating CIP RT kernel to 4.19.50 - Pavel

#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html

4. Work out a solution for LAVA master backups - patersonc

* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190711/b9494b78/attachment-0001.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-07-04  0:59 SZ Lin (林上智)
@ 2019-07-04  6:38 ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-07-04  6:38 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

Today, Daniel-san takes a day off because of sickness.
And I won't join the meeting because I have an another plan.
Sorry about that.

So I'll describe the update of SW Updates WG here before the meeting.

> * Software update
* We are preparing a software update demo for OSSJ.
* We had a meeting with Christian of Siemens and he shared a sample script
  that could manage the state of software update.
* Suzuki implemented the state management into the u-boot script of the demo
  and now BeagleBone Black can switch back to old root filesystem if the update fails.
  We call it "rollback".
* Now we can give the demo of raw image update only.
  If we can make it in time, we will give the demo of binary delta update using librsync.

Best regards,
Suzuki


> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (??
> ?)
> Sent: Thursday, July 04, 2019 10:00 AM
> To: cip-dev at 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 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=2019&month=7&day=4&hour=9&min=0&sec=0&p1=241&p2=137&
> p3=179&p4=136&p5=37&p6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * Action item
> 1. Provide the script for CIP kernel config collection - bwh
> #link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html
> 2. List real time kernel questions to ask Daniel Wagner - szlin
> 3. Try updating CIP RT kernel to 4.19.50 - Pavel
> #link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html
> 4. Work out a solution for LAVA master backups - patersonc
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-07-04  0:59 SZ Lin (林上智)
  2019-07-04  6:38 ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-07-04  0:59 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=7&day=4&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the script for CIP kernel config collection - bwh
#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html
2. List real time kernel questions to ask Daniel Wagner - szlin
3. Try updating CIP RT kernel to 4.19.50 - Pavel
#link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002548.html
4. Work out a solution for LAVA master backups - patersonc
* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-06-27  0:29 SZ Lin (林上智)
@ 2019-06-27  5:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: nobuhiro1.iwamatsu at toshiba.co.jp @ 2019-06-27  5:53 UTC (permalink / raw)
  To: cip-dev

Hi, SZ.

Sorry, I can not join today's IRC meeting by personal reason.

> * Kernel maintenance updates

I reviewd v4.4.163, and I released v4.4.182-cip34 and v4.19.52-cip4.
And I am working 
I am testing to release a CIP kernel based on v4.19.56 tomorrow.

Best regards,
  Nobuhiro

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, June 27, 2019 9:29 AM
> To: cip-dev at 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 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=2019
> &month=6&day=27&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37
> &p6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * Action item
> 1. Provide the script for CIP kernel config collection - bwh 2. List real
> time kernel questions to ask Daniel Wagner - szlin 3. Try updating CIP
> RT kernel to 4.19.50 - Pavel
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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.
> 
> I won't be able to attend this meeting, Gavin will chair today's meeting.
> 
> Best regards,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-06-27  0:29 SZ Lin (林上智)
  2019-06-27  5:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-06-27  0:29 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=6&day=27&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Provide the script for CIP kernel config collection - bwh
2. List real time kernel questions to ask Daniel Wagner - szlin
3. Try updating CIP RT kernel to 4.19.50 - Pavel
* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

I won't be able to attend this meeting, Gavin will chair today's meeting.

Best regards,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-06-20  1:11 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-06-20  1:11 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=6&day=20&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Send investigating email for kernel-testing lab to cip-dev - patersonc
2. Provide the script for CIP kernel config collection - bwh
3. List some questions to ask Daniel Wagner - szlin
* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-06-12 23:26 SZ Lin (林上智)
@ 2019-06-13  6:56 ` Chris Paterson
  0 siblings, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2019-06-13  6:56 UTC (permalink / raw)
  To: cip-dev

Hello SZ,

> From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-
> project.org> On Behalf Of SZ Lin (???)
> Sent: 13 June 2019 00:27
> 
> Hi all,
> 
> Kindly be reminded to attend the weekly meeting through IRC to discuss
> technical topics with CIP kernel today.
> 
> *Please note that 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=2019
> &month=6&day=13&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=1
> 36&p5=37&p6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * Action item
> 1. send investigating email for kernel-testing lab to cip-dev - patersonc

Sorry for the delay, I'm still waiting on an internal discussion to conclude before making a proposal to CIP.
Hopefully I'll get this done by next week.

Kind regards, Chris

> 2. provide the script for CIP kernel config collection - bwh
> 3. provide the plan about next cip-rt kernel release - szlin
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-06-12 23:26 SZ Lin (林上智)
  2019-06-13  6:56 ` Chris Paterson
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-06-12 23:26 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=6&day=13&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. send investigating email for kernel-testing lab to cip-dev - patersonc
2. provide the script for CIP kernel config collection - bwh
3. provide the plan about next cip-rt kernel release - szlin

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-06-06  1:28 SZ Lin (林上智)
@ 2019-06-06  2:01 ` kazuhiro3.hayashi at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: kazuhiro3.hayashi at toshiba.co.jp @ 2019-06-06  2:01 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

Sorry, I cannot attend the IRC meeting today.

Here are several updates from CIP-Core WG:

* Create patches so that isar-cip-core supports RZ/G1M iwg20m boards (on going)
* Create the "Debian 10 buster" based demonstration layers in deby,
  that supports QEMU x86 64bit and BeagleBone Black
* Held the first CIP-Core WG meeting and share the basic maintenance policies.
  Also planning to hold the second meeting to make a decision (or define action items)
  about the decision process of CIP maintained package list.

Best regards,
Kazu

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of SZ Lin (??
> ?)
> Sent: Thursday, June 6, 2019 10:28 AM
> To: cip-dev at 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 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=2019&month=6&day=6&hour=9&min=0&sec=0&p1=241&p2=137&
> p3=179&p4=136&p5=37&p6=248
> 
> US-West US-East?? UK???? DE???? TW???? JP
> 02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * Action item
> 1. send investigating email for kernel-testing lab to cip-dev - patersonc
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> 
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-06-06  1:28 SZ Lin (林上智)
  2019-06-06  2:01 ` kazuhiro3.hayashi at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-06-06  1:28 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=6&day=6&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. send investigating email for kernel-testing lab to cip-dev - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-05-30  1:18 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-05-30  1:18 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=5&day=30&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Prepare the CIP kernel release tutorial- Iwamatsu
2. Add license file in classify-failed-patches - Iwamatsu
3. send investigating email for kernel-testing lab to cip-dev - patersonc

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-05-23  1:58 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-05-23  1:58 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=5&day=23&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Upload check script to lts-commit-list repository - Pavel?
2. Release 4.4 and 4.19 kernel - Iwamatsu
3. Prepare the CIP kernel release document - Iwamatsu
4. Arrange a meeting between CIP core and CIP security WG - szlin

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-05-16  3:55 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-05-16  3:55 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=5&day=16&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East?? UK???? DE???? TW???? JP
02:00??? 05:00?? 10:00?? 11:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Action item
1. Send list of binary packages to cip-dev - kazu
* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-05-09  1:45 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-05-09  1:45 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=5&day=9&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190509/3f12121a/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-04-02  6:45                         ` Christian Storm
  2019-04-02  8:14                           ` akihiro27.suzuki at toshiba.co.jp
@ 2019-04-26 10:34                           ` akihiro27.suzuki at toshiba.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-04-26 10:34 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

Sorry for my late reply.
I was a little busy with work unrelated to CIP.

I tried Lua handler and I was able to understand it a little.
I referred to the following example.
<https://github.com/andi8086/meta-iot2000/blob/iot2000-ebg-swu/meta-iot2000-example/recipes-support/swupdate/swupdate/swupdate_handlers.lua>

I made "sw-description" and "swupdate_handlers.lua" for BBB.
They are working fine for now.
BTW, I needed to patch "0001-Fix-Lua-handler-issue.patch" to SWUpdate.

I think I'm ready, so I'd like to have a meeting with you.
However, Japan has consecutive national holidays from tomorrow to May 6th.
Could you please wait until the holidays end?
After the holidays, I'll let you know my several convenient time for the meeting.

Best regards,
Suzuki

> -----Original Message-----
> From: suzuki akihiro(???? ???? ????????????????)
> Sent: Tuesday, April 02, 2019 5:14 PM
> To: Christian Storm <christian.storm@siemens.com>; cip-dev at lists.cip-project.org
> Subject: RE: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Christian,
> 
> > > > OK, then I'd propose having a meeting about this so that I can explain how this
> > > > variant works and how we make use of it. When do you think you'll come to this
> > > > point so that a meeting makes sense?
> > >
> > > Thank you for your proposal.
> > > Just in case, please let me make sure the meaning of your proposal.
> > >
> > > Which one did you mean?
> > >
> > >   (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
> > >   (B) I should have a meeting after I implemented the A/B update by using Lua handler.
> > >
> > > If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
> > > because I haven't used it.
> > >
> > > If you meant (B), I will have a meeting after implementing it,
> > > but maybe the implementation (and tests) will take at least 1 month.
> >
> > I meant (A) to spare you (re)exploring the path I went :)
> > I'd like to show off some features you may find useful along the way as
> > well. Just let me know when you're ready and I'll setup the metting
> > then.
> 
> OK, I see. Thanks a lot!
> I'll let you know when I'm ready.
> 
> Best regards,
> Suzuki
> 
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> > Storm
> > Sent: Tuesday, April 02, 2019 3:46 PM
> > To: cip-dev at lists.cip-project.org
> > Subject: Re: [cip-dev] CIP IRC weekly meeting today
> >
> > Hi Suzuki,
> >
> > > > > > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > > > > > how to do round-robin A/B firmware update. That said, this is in my very
> > > > > > personal opinion a bit too involved and spread out over too many places.
> > > > > > That was also one reason I brought forward the Lua handler feature that
> > > > > > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > > > > > on par with C handlers by now, i.e., they are equally powerful. So, you
> > > > > > can write a Lua handler that does the target partition round-robin
> > > > > > calculation, flashing, and updating of the bootloader environment in one
> > > > > > place. The sw-description becomes simpler as well since you don't need
> > > > > > to specify the A/B layout there but instead the Lua handler will take
> > > > > > care of this.
> > > > > That makes sense.
> > > > > I thought that the A/B update way adopted by meta-swupdate-boards was
> > > > > a little difficult to understand and not very flexible.
> > > > > I would like to use Lua handler to implement the flexible A/B update
> > > > > which can be used in various situations.
> > > >
> > > > OK, then I'd propose having a meeting about this so that I can explain how this
> > > > variant works and how we make use of it. When do you think you'll come to this
> > > > point so that a meeting makes sense?
> > >
> > > Thank you for your proposal.
> > > Just in case, please let me make sure the meaning of your proposal.
> > >
> > > Which one did you mean?
> > >
> > >   (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
> > >   (B) I should have a meeting after I implemented the A/B update by using Lua handler.
> > >
> > > If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
> > > because I haven't used it.
> > >
> > > If you meant (B), I will have a meeting after implementing it,
> > > but maybe the implementation (and tests) will take at least 1 month.
> >
> > I meant (A) to spare you (re)exploring the path I went :)
> > I'd like to show off some features you may find useful along the way as
> > well. Just let me know when you're ready and I'll setup the metting
> > then.
> >
> >
> > Kind regards,
> >    Christian
> >
> > --
> > Dr. Christian Storm
> > Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> > Otto-Hahn-Ring 6, 81739 M??nchen, Germany
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sw-description
Type: application/octet-stream
Size: 201 bytes
Desc: sw-description
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190426/2734cf4a/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swupdate_handlers.lua
Type: application/octet-stream
Size: 2294 bytes
Desc: swupdate_handlers.lua
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190426/2734cf4a/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fix-Lua-handler-issue.patch
Type: application/octet-stream
Size: 1478 bytes
Desc: 0001-Fix-Lua-handler-issue.patch
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190426/2734cf4a/attachment-0002.obj>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-04-25  2:34 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-04-25  2:34 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that 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=2019&month=4&day=18&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248



US-West US-East   UK     DE     TW     JP

02:00    05:00   10:00   11:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* AI review

#action The review results from Pavel will be confirmed - Iwamatsu-san

#action send the patch to Jan for reviewing - kazu

#action deby: update "cip-core_buster" branch ? kazu



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190425/0daafc2f/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-04-18  1:33 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-04-18  1:33 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=4&day=18&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Send discussion of deby naming to cip-dev - Kazu
#action The review results from Pavel will be confirmed - Iwamatsu-san
#action Ask the status of Plathome's lab ? szlin
-> Done
#action Re-open the discussion with package list supported in CIP in cip-dev ? Kazu
->Done

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-04-11  2:28 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-04-11  2:28 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=4&day=11&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Send email to Daniel for SW update update ? szlin
-> Done
#action Daniel has to upload to the wiki the SW updates tool comparison document
-> Done
#action Send discussion of deby naming to cip-dev - Kazu
#action The review results from Pavel will be confirmed - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-04-04  2:52 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-04-04  2:52 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that 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=2019&month=4&day=4&hour=9&min=0&sec=0&p1=241&p2=137&p3=179&p4=136&p5=37&p6=248

US-West US-East   UK     DE     TW     JP
02:00    05:00   10:00   11:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Iwamatsu-san will re-upload the 4.4.176-cip31
-> Done
#action The proposal of CIP identifiers in patch submissions will send to cip-dev ? Chris
-> Done
#action Ask for the permission in patchwork - szlin
-> Done (Thanks to Chris!)
#action Discuss the naming of deby in TSC - Daniel Sangorrin
#action Daniel has to upload to the wiki the SW updates tool comparison document
#action The review results from Pavel will be confirmed - Iwamatsu-san

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-04-02  6:45                         ` Christian Storm
@ 2019-04-02  8:14                           ` akihiro27.suzuki at toshiba.co.jp
  2019-04-26 10:34                           ` akihiro27.suzuki at toshiba.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-04-02  8:14 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

> > > OK, then I'd propose having a meeting about this so that I can explain how this
> > > variant works and how we make use of it. When do you think you'll come to this
> > > point so that a meeting makes sense?
> >
> > Thank you for your proposal.
> > Just in case, please let me make sure the meaning of your proposal.
> >
> > Which one did you mean?
> >
> >   (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
> >   (B) I should have a meeting after I implemented the A/B update by using Lua handler.
> >
> > If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
> > because I haven't used it.
> >
> > If you meant (B), I will have a meeting after implementing it,
> > but maybe the implementation (and tests) will take at least 1 month.
> 
> I meant (A) to spare you (re)exploring the path I went :)
> I'd like to show off some features you may find useful along the way as
> well. Just let me know when you're ready and I'll setup the metting
> then.

OK, I see. Thanks a lot!
I'll let you know when I'm ready.

Best regards,
Suzuki


> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> Storm
> Sent: Tuesday, April 02, 2019 3:46 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Suzuki,
> 
> > > > > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > > > > how to do round-robin A/B firmware update. That said, this is in my very
> > > > > personal opinion a bit too involved and spread out over too many places.
> > > > > That was also one reason I brought forward the Lua handler feature that
> > > > > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > > > > on par with C handlers by now, i.e., they are equally powerful. So, you
> > > > > can write a Lua handler that does the target partition round-robin
> > > > > calculation, flashing, and updating of the bootloader environment in one
> > > > > place. The sw-description becomes simpler as well since you don't need
> > > > > to specify the A/B layout there but instead the Lua handler will take
> > > > > care of this.
> > > > That makes sense.
> > > > I thought that the A/B update way adopted by meta-swupdate-boards was
> > > > a little difficult to understand and not very flexible.
> > > > I would like to use Lua handler to implement the flexible A/B update
> > > > which can be used in various situations.
> > >
> > > OK, then I'd propose having a meeting about this so that I can explain how this
> > > variant works and how we make use of it. When do you think you'll come to this
> > > point so that a meeting makes sense?
> >
> > Thank you for your proposal.
> > Just in case, please let me make sure the meaning of your proposal.
> >
> > Which one did you mean?
> >
> >   (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
> >   (B) I should have a meeting after I implemented the A/B update by using Lua handler.
> >
> > If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
> > because I haven't used it.
> >
> > If you meant (B), I will have a meeting after implementing it,
> > but maybe the implementation (and tests) will take at least 1 month.
> 
> I meant (A) to spare you (re)exploring the path I went :)
> I'd like to show off some features you may find useful along the way as
> well. Just let me know when you're ready and I'll setup the metting
> then.
> 
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M?nchen, Germany
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-04-02  3:50                       ` akihiro27.suzuki at toshiba.co.jp
@ 2019-04-02  6:45                         ` Christian Storm
  2019-04-02  8:14                           ` akihiro27.suzuki at toshiba.co.jp
  2019-04-26 10:34                           ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: Christian Storm @ 2019-04-02  6:45 UTC (permalink / raw)
  To: cip-dev

Hi Suzuki,

> > > > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > > > how to do round-robin A/B firmware update. That said, this is in my very
> > > > personal opinion a bit too involved and spread out over too many places.
> > > > That was also one reason I brought forward the Lua handler feature that
> > > > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > > > on par with C handlers by now, i.e., they are equally powerful. So, you
> > > > can write a Lua handler that does the target partition round-robin
> > > > calculation, flashing, and updating of the bootloader environment in one
> > > > place. The sw-description becomes simpler as well since you don't need
> > > > to specify the A/B layout there but instead the Lua handler will take
> > > > care of this.
> > > That makes sense.
> > > I thought that the A/B update way adopted by meta-swupdate-boards was
> > > a little difficult to understand and not very flexible.
> > > I would like to use Lua handler to implement the flexible A/B update
> > > which can be used in various situations.
> > 
> > OK, then I'd propose having a meeting about this so that I can explain how this
> > variant works and how we make use of it. When do you think you'll come to this
> > point so that a meeting makes sense?
> 
> Thank you for your proposal.
> Just in case, please let me make sure the meaning of your proposal.
> 
> Which one did you mean?
> 
>   (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
>   (B) I should have a meeting after I implemented the A/B update by using Lua handler.
> 
> If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
> because I haven't used it.
> 
> If you meant (B), I will have a meeting after implementing it,
> but maybe the implementation (and tests) will take at least 1 month.

I meant (A) to spare you (re)exploring the path I went :)
I'd like to show off some features you may find useful along the way as
well. Just let me know when you're ready and I'll setup the metting
then.


Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-04-01  6:48                     ` Christian Storm
@ 2019-04-02  3:50                       ` akihiro27.suzuki at toshiba.co.jp
  2019-04-02  6:45                         ` Christian Storm
  0 siblings, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-04-02  3:50 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

> > > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > > how to do round-robin A/B firmware update. That said, this is in my very
> > > personal opinion a bit too involved and spread out over too many places.
> > > That was also one reason I brought forward the Lua handler feature that
> > > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > > on par with C handlers by now, i.e., they are equally powerful. So, you
> > > can write a Lua handler that does the target partition round-robin
> > > calculation, flashing, and updating of the bootloader environment in one
> > > place. The sw-description becomes simpler as well since you don't need
> > > to specify the A/B layout there but instead the Lua handler will take
> > > care of this.
> > That makes sense.
> > I thought that the A/B update way adopted by meta-swupdate-boards was
> > a little difficult to understand and not very flexible.
> > I would like to use Lua handler to implement the flexible A/B update
> > which can be used in various situations.
> 
> OK, then I'd propose having a meeting about this so that I can explain how this
> variant works and how we make use of it. When do you think you'll come to this
> point so that a meeting makes sense?

Thank you for your proposal.
Just in case, please let me make sure the meaning of your proposal.

Which one did you mean?

  (A) In a meeting, you will tell me about how to use Lua handler for the A/B update.
  (B) I should have a meeting after I implemented the A/B update by using Lua handler.

If you meant (A), I'd like some time, 1 or 2 weeks, to try Lua before the meeting
because I haven't used it.

If you meant (B), I will have a meeting after implementing it,
but maybe the implementation (and tests) will take at least 1 month.

Best regards,
Suzuki


> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> Storm
> Sent: Monday, April 01, 2019 3:49 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Suzuki,
> 
> > > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > > how to do round-robin A/B firmware update. That said, this is in my very
> > > personal opinion a bit too involved and spread out over too many places.
> > > That was also one reason I brought forward the Lua handler feature that
> > > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > > on par with C handlers by now, i.e., they are equally powerful. So, you
> > > can write a Lua handler that does the target partition round-robin
> > > calculation, flashing, and updating of the bootloader environment in one
> > > place. The sw-description becomes simpler as well since you don't need
> > > to specify the A/B layout there but instead the Lua handler will take
> > > care of this.
> > That makes sense.
> > I thought that the A/B update way adopted by meta-swupdate-boards was
> > a little difficult to understand and not very flexible.
> > I would like to use Lua handler to implement the flexible A/B update
> > which can be used in various situations.
> 
> OK, then I'd propose having a meeting about this so that I can explain
> how this
> variant works and how we make use of it. When do you think you'll come
> to this
> point so that a meeting makes sense?
> 
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M?nchen, Germany
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-04-01  2:48                   ` akihiro27.suzuki at toshiba.co.jp
@ 2019-04-01  6:48                     ` Christian Storm
  2019-04-02  3:50                       ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: Christian Storm @ 2019-04-01  6:48 UTC (permalink / raw)
  To: cip-dev

Hi Suzuki,

> > Ah, OK. This is the "official" in the sense of exemplary implemented way
> > how to do round-robin A/B firmware update. That said, this is in my very
> > personal opinion a bit too involved and spread out over too many places.
> > That was also one reason I brought forward the Lua handler feature that
> > allows you to implement a handler in Lua. Lua handlers are feature-wise
> > on par with C handlers by now, i.e., they are equally powerful. So, you
> > can write a Lua handler that does the target partition round-robin
> > calculation, flashing, and updating of the bootloader environment in one
> > place. The sw-description becomes simpler as well since you don't need
> > to specify the A/B layout there but instead the Lua handler will take
> > care of this.
> That makes sense.
> I thought that the A/B update way adopted by meta-swupdate-boards was
> a little difficult to understand and not very flexible.
> I would like to use Lua handler to implement the flexible A/B update
> which can be used in various situations.

OK, then I'd propose having a meeting about this so that I can explain how this
variant works and how we make use of it. When do you think you'll come to this
point so that a meeting makes sense?


Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-29 13:21                 ` Christian Storm
@ 2019-04-01  2:48                   ` akihiro27.suzuki at toshiba.co.jp
  2019-04-01  6:48                     ` Christian Storm
  0 siblings, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-04-01  2:48 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

> This is because SWUpdate is designed around a multi-process model with
> IPC among the processes via sockets. This has, as one example, the
> benefit that one can run the multiple components of SWUpdate with
> different privileges. Apart from this, there's a clean interface also
> imposed on the code structure which helps the modularization of the
> source code.
I understand. Thank you for the explanation.

> Ah, OK. This is the "official" in the sense of exemplary implemented way
> how to do round-robin A/B firmware update. That said, this is in my very
> personal opinion a bit too involved and spread out over too many places.
> That was also one reason I brought forward the Lua handler feature that
> allows you to implement a handler in Lua. Lua handlers are feature-wise
> on par with C handlers by now, i.e., they are equally powerful. So, you
> can write a Lua handler that does the target partition round-robin
> calculation, flashing, and updating of the bootloader environment in one
> place. The sw-description becomes simpler as well since you don't need
> to specify the A/B layout there but instead the Lua handler will take
> care of this.
That makes sense.
I thought that the A/B update way adopted by meta-swupdate-boards was
a little difficult to understand and not very flexible.
I would like to use Lua handler to implement the flexible A/B update
which can be used in various situations.

Best regards,
Suzuki

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> Storm
> Sent: Friday, March 29, 2019 10:22 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Suzuki,
> 
> 
> > I'm sorry to bother you.
> 
> You're always welcome.
> 
> 
> > > Looks good as / is mounted ro. Question is whether this is done via
> a
> > > remount,ro or whether it's ro right from the start?
> > I didn't remount / with ro manually,
> > but I have found that /proc/cmdline of the booted BBB includes "rw"
> as follows:
> >
> >     root at beaglebone:~# cat /proc/cmdline
> >     console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 rw
> rootfstype=ext4 rootwait
> >
> > This is because "args_mmc" (the environment variable of u-boot) was
> not changed
> > even though I had built the rootfs with "read-only-rootfs" option in
> poky.
> > (Although "/" in /etc/fstab was changed from "rw" to "ro" by the option)
> >
> > The "args_mmc" was as follows:
> >
> >     args_mmc=run finduuid;setenv bootargs console=${console}
> ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
> >
> > When I changed "rw" on args_mmc to "ro" and booted the BBB, /proc/cmdline
> was changed as follows:
> >
> >     root at beaglebone:~# cat /proc/cmdline
> >     console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 ro
> rootfstype=ext4 rootwait
> >
> > Because of this, the rootfs came to able to be mounted with ro from
> the start.
> > Actually, I booted the BBB on several times,
> > and I checked that there were no changes in the partition.
> > Of course the binary delta update was successful with this
> configuration.
> > It seems for me that this issue has been resolved.
> > Thank you for your great help!
> 
> That sounds good! Glad I could help here.
> 
> 
> > BTW, I have found the cause of the ext4 error messages.
> > This is because "/run/utmp" and "/run/mount" were created
> > before "/" was remounted automatically with ro according to /etc/fstab
> in the boot process.
> > Their inodes were created but they were overwritten by zero by the binary
> delta update.
> > But the inode of /run, their parent directory, was not overwritten by
> the update,
> > and the dentries of "utmp" and "mount" remained inside the inode of
> /run.
> > So the ext4 error messages were shown.
> > Currently, "utmp" and "mount" are not created because I can boot the
> rootfs with "ro" from the start.
> > So this issue does not occur.
> 
> Sounds reasonable, good to have it sorted out.
> 
> 
> > > Well, how did you instruct SWUpdate to choose "copy1" or "copy2"?
> > Sorry for the lack of explanation.
> > I used the method adopted by meta-swupdate-boards.
> > The important file is the following startup script of swupdate.
> >
> <https://github.com/sbabic/meta-swupdate-boards/blob/master/recipes-
> support/swupdate/swupdate/beaglebone/swupdate>
> > The script checks the current rootfs partition and executes swupdate
> with "-e stable,copy{1|2}" as follows:
> >
> >     root at beaglebone:~# cat /etc/init.d/swupdate
> >     #! /bin/sh
> >     -------- (snip) --------
> >     DAEMON=/usr/bin/swupdate
> >     -------- (snip) --------
> >     rootfs=`mount | grep "on / type" | cut -d':' -f 2 | cut -d' ' -f
> 1`
> >
> >     if [ $rootfs == '/dev/mmcblk1p2' ];then
> >             selection="-e stable,copy2"
> >     else
> >             selection="-e stable,copy1"
> >     fi
> >     -------- (snip) --------
> >     exec $DAEMON -v -H beaglebone:1.0 ${selection} -f
> /etc/swupdate.cfg -u "$EXTRA_ARGS" -w "" &
> >     -------- (snip) --------
> >
> > If the BBB is booted from /dev/mmcblk1p2, swupdate is executed with
> "-e stable,copy2" as follows:
> >
> >     root at beaglebone:~# ps aux | grep swupdate
> >     root       500  0.0  0.2   1704  1164 ?        S    13:15
> 0:00 /usr/bin/swupdate-progress -w -p -r
> >     root       501  0.2  1.2  49456  6504 ?        Sl   13:15
> 0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f
> /etc/swupdate.cfg -u  -w
> >     root       522  0.2  0.7  31016  3868 ?        Sl   13:15
> 0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f
> /etc/swupdate.cfg -u  -w
> >     root       524  0.0  0.9  24200  4840 ?        S    13:15
> 0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f
> /etc/swupdate.cfg -u  -w
> >     root       551  0.0  0.2   1884  1040 ttyO0    S+   13:19
> 0:00 grep swupdate
> >     (I'm not sure why /usr/bin/swupdate is running with 3 processes)
> 
> This is because SWUpdate is designed around a multi-process model with
> IPC among the processes via sockets. This has, as one example, the
> benefit that one can run the multiple components of SWUpdate with
> different privileges. Apart from this, there's a clean interface also
> imposed on the code structure which helps the modularization of the
> source code.
> 
> 
> > If you update now, the rule described in the "copy2" section in
> sw-description is used.
> > In the sw-description which was attached in my previous email,
> > the update target in the "copy2" section is /dev/mmcblk1p3.
> > Besides, bootcmd_legacy_mmc1 (the environment variable of u-boot)
> > is modified to use /dev/mmcblk1p3 as the next boot target.
> > If the BBB is booted from /dev/mmcblk1p3, the "copy1" section is used.
> > In the "copy1" section, the update and next boot target are
> /dev/mmcblk1p2.
> 
> Ah, OK. This is the "official" in the sense of exemplary implemented way
> how to do round-robin A/B firmware update. That said, this is in my very
> personal opinion a bit too involved and spread out over too many places.
> That was also one reason I brought forward the Lua handler feature that
> allows you to implement a handler in Lua. Lua handlers are feature-wise
> on par with C handlers by now, i.e., they are equally powerful. So, you
> can write a Lua handler that does the target partition round-robin
> calculation, flashing, and updating of the bootloader environment in one
> place. The sw-description becomes simpler as well since you don't need
> to specify the A/B layout there but instead the Lua handler will take
> care of this.
> 
> 
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M?nchen, Germany
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-27  8:25               ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-29 13:21                 ` Christian Storm
  2019-04-01  2:48                   ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: Christian Storm @ 2019-03-29 13:21 UTC (permalink / raw)
  To: cip-dev

Hi Suzuki,


> I'm sorry to bother you.

You're always welcome.


> > Looks good as / is mounted ro. Question is whether this is done via a
> > remount,ro or whether it's ro right from the start?
> I didn't remount / with ro manually,
> but I have found that /proc/cmdline of the booted BBB includes "rw" as follows:
> 
>     root at beaglebone:~# cat /proc/cmdline
>     console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 rw rootfstype=ext4 rootwait
> 
> This is because "args_mmc" (the environment variable of u-boot) was not changed
> even though I had built the rootfs with "read-only-rootfs" option in poky.
> (Although "/" in /etc/fstab was changed from "rw" to "ro" by the option)
> 
> The "args_mmc" was as follows:
> 
>     args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
> 
> When I changed "rw" on args_mmc to "ro" and booted the BBB, /proc/cmdline was changed as follows:
> 
>     root at beaglebone:~# cat /proc/cmdline
>     console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 ro rootfstype=ext4 rootwait
> 
> Because of this, the rootfs came to able to be mounted with ro from the start.
> Actually, I booted the BBB on several times,
> and I checked that there were no changes in the partition.
> Of course the binary delta update was successful with this configuration.
> It seems for me that this issue has been resolved.
> Thank you for your great help!

That sounds good! Glad I could help here.


> BTW, I have found the cause of the ext4 error messages.
> This is because "/run/utmp" and "/run/mount" were created
> before "/" was remounted automatically with ro according to /etc/fstab in the boot process.
> Their inodes were created but they were overwritten by zero by the binary delta update.
> But the inode of /run, their parent directory, was not overwritten by the update,
> and the dentries of "utmp" and "mount" remained inside the inode of /run.
> So the ext4 error messages were shown.
> Currently, "utmp" and "mount" are not created because I can boot the rootfs with "ro" from the start.
> So this issue does not occur.

Sounds reasonable, good to have it sorted out.


> > Well, how did you instruct SWUpdate to choose "copy1" or "copy2"?
> Sorry for the lack of explanation.
> I used the method adopted by meta-swupdate-boards.
> The important file is the following startup script of swupdate.
> <https://github.com/sbabic/meta-swupdate-boards/blob/master/recipes-support/swupdate/swupdate/beaglebone/swupdate>
> The script checks the current rootfs partition and executes swupdate with "-e stable,copy{1|2}" as follows:
> 
>     root at beaglebone:~# cat /etc/init.d/swupdate
>     #! /bin/sh
>     -------- (snip) --------
>     DAEMON=/usr/bin/swupdate
>     -------- (snip) --------
>     rootfs=`mount | grep "on / type" | cut -d':' -f 2 | cut -d' ' -f 1`
> 
>     if [ $rootfs == '/dev/mmcblk1p2' ];then
>             selection="-e stable,copy2"
>     else
>             selection="-e stable,copy1"
>     fi
>     -------- (snip) --------
>     exec $DAEMON -v -H beaglebone:1.0 ${selection} -f /etc/swupdate.cfg -u "$EXTRA_ARGS" -w "" &
>     -------- (snip) --------
> 
> If the BBB is booted from /dev/mmcblk1p2, swupdate is executed with "-e stable,copy2" as follows:
> 
>     root at beaglebone:~# ps aux | grep swupdate
>     root       500  0.0  0.2   1704  1164 ?        S    13:15   0:00 /usr/bin/swupdate-progress -w -p -r
>     root       501  0.2  1.2  49456  6504 ?        Sl   13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
>     root       522  0.2  0.7  31016  3868 ?        Sl   13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
>     root       524  0.0  0.9  24200  4840 ?        S    13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
>     root       551  0.0  0.2   1884  1040 ttyO0    S+   13:19   0:00 grep swupdate
>     (I'm not sure why /usr/bin/swupdate is running with 3 processes)

This is because SWUpdate is designed around a multi-process model with
IPC among the processes via sockets. This has, as one example, the
benefit that one can run the multiple components of SWUpdate with
different privileges. Apart from this, there's a clean interface also
imposed on the code structure which helps the modularization of the
source code.


> If you update now, the rule described in the "copy2" section in sw-description is used.
> In the sw-description which was attached in my previous email,
> the update target in the "copy2" section is /dev/mmcblk1p3.
> Besides, bootcmd_legacy_mmc1 (the environment variable of u-boot)
> is modified to use /dev/mmcblk1p3 as the next boot target.
> If the BBB is booted from /dev/mmcblk1p3, the "copy1" section is used.
> In the "copy1" section, the update and next boot target are /dev/mmcblk1p2.

Ah, OK. This is the "official" in the sense of exemplary implemented way
how to do round-robin A/B firmware update. That said, this is in my very
personal opinion a bit too involved and spread out over too many places.
That was also one reason I brought forward the Lua handler feature that
allows you to implement a handler in Lua. Lua handlers are feature-wise
on par with C handlers by now, i.e., they are equally powerful. So, you
can write a Lua handler that does the target partition round-robin
calculation, flashing, and updating of the bootloader environment in one
place. The sw-description becomes simpler as well since you don't need
to specify the A/B layout there but instead the Lua handler will take
care of this.



Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-03-28  4:08 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-03-28  4:08 UTC (permalink / raw)
  To: cip-dev

Hi all,



Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*



US-West US-East  UK    DE     TW     JP

02:00    05:00   09:00   10:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* AI review

#action Please send configuration file of kernel 4.19 to cip-dev before the end of March.

#action Daniel has to upload to the wiki the SW updates tool comparison document

#action Add a link to the SW updates wiki page from the embedded world CIP release page



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190328/9afaa154/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-22 12:37             ` Christian Storm
@ 2019-03-27  8:25               ` akihiro27.suzuki at toshiba.co.jp
  2019-03-29 13:21                 ` Christian Storm
  0 siblings, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-27  8:25 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

I'm sorry to bother you.

> Looks good as / is mounted ro. Question is whether this is done via a
> remount,ro or whether it's ro right from the start?
I didn't remount / with ro manually,
but I have found that /proc/cmdline of the booted BBB includes "rw" as follows:

    root at beaglebone:~# cat /proc/cmdline
    console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 rw rootfstype=ext4 rootwait

This is because "args_mmc" (the environment variable of u-boot) was not changed
even though I had built the rootfs with "read-only-rootfs" option in poky.
(Although "/" in /etc/fstab was changed from "rw" to "ro" by the option)

The "args_mmc" was as follows:

    args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}

When I changed "rw" on args_mmc to "ro" and booted the BBB, /proc/cmdline was changed as follows:

    root at beaglebone:~# cat /proc/cmdline
    console=ttyO0,115200n8 root=PARTUUID=770dcaeb-02 ro rootfstype=ext4 rootwait

Because of this, the rootfs came to able to be mounted with ro from the start.
Actually, I booted the BBB on several times,
and I checked that there were no changes in the partition.
Of course the binary delta update was successful with this configuration.
It seems for me that this issue has been resolved.
Thank you for your great help!

BTW, I have found the cause of the ext4 error messages.
This is because "/run/utmp" and "/run/mount" were created
before "/" was remounted automatically with ro according to /etc/fstab in the boot process.
Their inodes were created but they were overwritten by zero by the binary delta update.
But the inode of /run, their parent directory, was not overwritten by the update,
and the dentries of "utmp" and "mount" remained inside the inode of /run.
So the ext4 error messages were shown.
Currently, "utmp" and "mount" are not created because I can boot the rootfs with "ro" from the start.
So this issue does not occur.

> Well, how did you instruct SWUpdate to choose "copy1" or "copy2"?
Sorry for the lack of explanation.
I used the method adopted by meta-swupdate-boards.
The important file is the following startup script of swupdate.
<https://github.com/sbabic/meta-swupdate-boards/blob/master/recipes-support/swupdate/swupdate/beaglebone/swupdate>
The script checks the current rootfs partition and executes swupdate with "-e stable,copy{1|2}" as follows:

    root at beaglebone:~# cat /etc/init.d/swupdate
    #! /bin/sh
    -------- (snip) --------
    DAEMON=/usr/bin/swupdate
    -------- (snip) --------
    rootfs=`mount | grep "on / type" | cut -d':' -f 2 | cut -d' ' -f 1`

    if [ $rootfs == '/dev/mmcblk1p2' ];then
            selection="-e stable,copy2"
    else
            selection="-e stable,copy1"
    fi
    -------- (snip) --------
    exec $DAEMON -v -H beaglebone:1.0 ${selection} -f /etc/swupdate.cfg -u "$EXTRA_ARGS" -w "" &
    -------- (snip) --------

If the BBB is booted from /dev/mmcblk1p2, swupdate is executed with "-e stable,copy2" as follows:

    root at beaglebone:~# ps aux | grep swupdate
    root       500  0.0  0.2   1704  1164 ?        S    13:15   0:00 /usr/bin/swupdate-progress -w -p -r
    root       501  0.2  1.2  49456  6504 ?        Sl   13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
    root       522  0.2  0.7  31016  3868 ?        Sl   13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
    root       524  0.0  0.9  24200  4840 ?        S    13:15   0:00 /usr/bin/swupdate -v -H beaglebone 1.0 -e stable,copy2 -f /etc/swupdate.cfg -u  -w
    root       551  0.0  0.2   1884  1040 ttyO0    S+   13:19   0:00 grep swupdate
    (I'm not sure why /usr/bin/swupdate is running with 3 processes)

If you update now, the rule described in the "copy2" section in sw-description is used.
In the sw-description which was attached in my previous email,
the update target in the "copy2" section is /dev/mmcblk1p3.
Besides, bootcmd_legacy_mmc1 (the environment variable of u-boot)
is modified to use /dev/mmcblk1p3 as the next boot target.
If the BBB is booted from /dev/mmcblk1p3, the "copy1" section is used.
In the "copy1" section, the update and next boot target are /dev/mmcblk1p2.

Best regards,
Suzuki

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> Storm
> Sent: Friday, March 22, 2019 9:37 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Suzuki,
> 
> > > > I mounted rootfs with read-only.
> > >
> > > OK, from the diffs it seems that temporary storage directories such
> as
> > > /run and /var/tmp are not separate mount points from your roots?
> > I built the rootfs image by poky with "read-only-rootfs" option like
> following URL.
> >
> <https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.h
> tml#creating-the-root-filesystem>
> 
> Ah, OK, didn't try that myself yet.
> 
> 
> > I think that the temporary storage directories were mounted as tmpfs
> as follows:
> >
> >     root at beaglebone:~# df -T
> >     Filesystem     Type     1K-blocks  Used Available Use% Mounted
> on
> >     /dev/root      ext4        135221 75902     49409  61% /
> >     devtmpfs       devtmpfs    243420     0    243420   0% /dev
> >     tmpfs          tmpfs       252124   124    252000   1% /run
> >     tmpfs          tmpfs       252124   252    251872   1%
> /var/volatile
> >
> >     root at beaglebone:~# mount
> >     /dev/mmcblk1p2 on / type ext4 (ro,relatime,data=ordered)
> >     devtmpfs on /dev type devtmpfs
> (rw,relatime,size=243420k,nr_inodes=60855,mode=755)
> >     proc on /proc type proc (rw,relatime)
> >     sysfs on /sys type sysfs (rw,relatime)
> >     debugfs on /sys/kernel/debug type debugfs (rw,relatime)
> >     tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
> >     tmpfs on /var/volatile type tmpfs (rw,relatime)
> >     devpts on /dev/pts type devpts
> (rw,relatime,gid=5,mode=620,ptmxmode=000)
> >     tmpfs on /var/lib type tmpfs (rw,relatime)
> 
> Looks good as / is mounted ro. Question is whether this is done via a
> remount,ro or whether it's ro right from the start?
> 
> To find out what's touching the files you can, e.g., turn on block_dump
> $ echo 1 > /proc/sys/vm/block_dump
> quite early in the boot process and filter it by grepping dmesg like
> $ dmesg | grep dirtied | grep "on sda" | sort
> 
> 
> > > > I checked the difference of the rootfs image between before boot
> and
> > > after boot,
> > > > and at least the number of mounts had changed.
> > > >
> > > > I attached following log files. I think that 0x434 is a mount count.
> > >
> > > You can use tune2fs -l /dev/<rootdevicenode> and look for
> > > "Mount count: <some number>" to verify this.
> > I checked this by tune2fs, and it was correct.
> >
> >     After the 1st boot:
> >
> >         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount
> count"
> >         Mount count:              1
> >
> >         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep
> 430
> >         00000430  81 43 6d 38 01 00 ff ff  53 ef 01 00 01 00 00 00
> |.Cm8....S.......|
> >
> >     After the 2nd boot:
> >
> >         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount
> count"
> >         Mount count:              2
> >
> >         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep
> 430
> >         00000430  f4 a4 90 5c 02 00 ff ff  53 ef 01 00 01 00 00 00
> |...\....S.......|
> >
> >     After the 3rd boot:
> >
> >         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount
> count"
> >         Mount count:              3
> >
> >         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep
> 430
> >         00000430  63 a6 90 5c 03 00 ff ff  53 ef 01 00 01 00 00 00
> |c..\....S.......|
> >
> > BTW, the values of "Last mount time", "Last write time" and "Lifetime
> writes" were also changed.
> >
> > I'm concerned that if the partition which is set to rdiffbase is changed
> as above,
> > the binary delta update will be done correctly or not.
> 
> Well, technically it's just a patch, so if there is a difference in the
> two partition images you diff, and be it the filesystem's mount count,
> then this will end up in the patch and be applied on the device. If
> that's deemed incorrect, then such filesystem metadata has to be
> excluded from the diff by means of preprocessing both partition images
> so that there's no difference in the metadata that could end up in the
> binary patch.
> 
> The resulting partition's data is copied from the partition designated
> by rdiffbase except for the patch contents that overrule these. So, to
> stay in the above example, if the filesystem's mount count is not in the
> binary patch, it's taken from rdiffbase.
> 
> 
> > > > BTW, the warning message after binary delta update was as follows:
> > > >
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm init: deleted inode referenced: 5040
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm init: deleted inode referenced: 5040
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > > comm mount: deleted inode referenced: 5833
> > >
> > > Well, my suspicion is that, after a delta-update of the partition,
> the
> > > filesystem's metadata is corrupt, i.e., the metdata was partially
> > > updated by a delta update, resulting in an inconsistent overall state.
> > > Could you elaborate on the exact steps you performed? Is the diff
> done
> > > from/to the right sources? Could as well be that the journal hasn't
> > > committed the changes... Just a wild guess though...
> > The exact steps I performed are as follows:
> >
> >      1. Build rootfs image as v1 by poky by reference to the following
> article:
> >
> <https://mkrak.org/2018/01/26/updating-embedded-linux-devices-part2/
> >
> >      2. Boot BeagleBone Black (BBB) from microSD
> >      3. Write "core-image-full-cmdline-beaglebone.wic" to
> /dev/mmcblk1 (eMMC) on BBB
> >      4. Write "core-image-full-cmdline-beaglebone.ext4" to
> /dev/mmcblk1p2
> >      5. Make /dev/mmcblk1p3 partition by fdisk and copy /dev/mmcblk1p2
> to /dev/mmcblk1p3
> >      6. Shutdown BBB and boot from /dev/mmcblk1p3
> >      7. Add a change to the recipe of poky and rebuild rootfs image
> as v2
> >      8. Make a delta image from v1 and v2 by rdiff command
> >      9. Make swu image from attached sw-description, emmcsetup.lua,
> and the delta image
> 
> Well, in the attached sw-description, you're using
> 						device =
> "/dev/mmcblk1p2";
> 						properties: {
> 							rdiffbase =
> ["/dev/mmcblk1p2"];
> 						};
> for "copy1" and
> 						device =
> "/dev/mmcblk1p3";
> 						properties: {
> 							rdiffbase =
> ["/dev/mmcblk1p3"];
> 						};
> for "copy2" which basically says use /dev/mmcblk1p{2,3} as rdiffbase
> (i.e. copy source) *and* target, hence you're overwriting
> /dev/mmcblk1p{2,3} with /dev/mmcblk1p{2,3} + binary patch applied.
> If /dev/mmcblk1p{2,3} happens to be mounted, then you'll get the ext4
> errors as you're overwriting a mounted filesystem on the block layer.
> 
> >     10. Access http://[IP address of BBB]:8080/ by Web browser and
> upload the above swu image
> >         (After the update is finished, It reboots automatically)
> 
> Well, how did you instruct SWUpdate to choose "copy1" or "copy2"?
> Can you provide the logs of the SWUpdate runs and the information from
> which partition you booted while running SWUpdate?
> 
> >     11. Check the update is done correctly
> >         (It boots from /dev/mmcblk1p2 and the rootfs image version is
> v2)
> 
> Well, I cannot tell about your setup but does
>   value = "... setenv bootpart 1:3 ..."
> in "copy2" instruct to boot from /dev/mmcblk1p2? Same question applies
> to "copy1".
> 
> >     12. Do the step of No.10 to update the rootfs image on /dev/mmcblk1p3
> to v2
> >     13. After updating and rebooting, BBB is booted from /dev/mmcblk1p3
> and
> >         the rootfs image version is v2, but the ext4 warning message
> is shown
> >
> > If you need more detailed steps, please let me know.
> >
> > To tell the truth, at first, I set the different partition to "device"
> and "rdiffbase" field at sw-description.
> > If "/dev/mmcblk1p2" was set to "device", I set "/dev/mmcblk1p3" to
> "rdiffbase" -- and vice versa.
> > When I used this sw-description, the ext4 warning message was shown
> at the step of No.11.
> 
> 
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M?nchen, Germany
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-22  5:01           ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-22 12:37             ` Christian Storm
  2019-03-27  8:25               ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: Christian Storm @ 2019-03-22 12:37 UTC (permalink / raw)
  To: cip-dev

Hi Suzuki,

> > > I mounted rootfs with read-only.
> >
> > OK, from the diffs it seems that temporary storage directories such as
> > /run and /var/tmp are not separate mount points from your roots?
> I built the rootfs image by poky with "read-only-rootfs" option like following URL.
> <https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#creating-the-root-filesystem>

Ah, OK, didn't try that myself yet.


> I think that the temporary storage directories were mounted as tmpfs as follows:
>
>     root at beaglebone:~# df -T
>     Filesystem     Type     1K-blocks  Used Available Use% Mounted on
>     /dev/root      ext4        135221 75902     49409  61% /
>     devtmpfs       devtmpfs    243420     0    243420   0% /dev
>     tmpfs          tmpfs       252124   124    252000   1% /run
>     tmpfs          tmpfs       252124   252    251872   1% /var/volatile
>
>     root at beaglebone:~# mount
>     /dev/mmcblk1p2 on / type ext4 (ro,relatime,data=ordered)
>     devtmpfs on /dev type devtmpfs (rw,relatime,size=243420k,nr_inodes=60855,mode=755)
>     proc on /proc type proc (rw,relatime)
>     sysfs on /sys type sysfs (rw,relatime)
>     debugfs on /sys/kernel/debug type debugfs (rw,relatime)
>     tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
>     tmpfs on /var/volatile type tmpfs (rw,relatime)
>     devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
>     tmpfs on /var/lib type tmpfs (rw,relatime)

Looks good as / is mounted ro. Question is whether this is done via a
remount,ro or whether it's ro right from the start?

To find out what's touching the files you can, e.g., turn on block_dump
$ echo 1 > /proc/sys/vm/block_dump
quite early in the boot process and filter it by grepping dmesg like
$ dmesg | grep dirtied | grep "on sda" | sort


> > > I checked the difference of the rootfs image between before boot and
> > after boot,
> > > and at least the number of mounts had changed.
> > >
> > > I attached following log files. I think that 0x434 is a mount count.
> >
> > You can use tune2fs -l /dev/<rootdevicenode> and look for
> > "Mount count: <some number>" to verify this.
> I checked this by tune2fs, and it was correct.
>
>     After the 1st boot:
>
>         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
>         Mount count:              1
>
>         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
>         00000430  81 43 6d 38 01 00 ff ff  53 ef 01 00 01 00 00 00  |.Cm8....S.......|
>
>     After the 2nd boot:
>
>         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
>         Mount count:              2
>
>         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
>         00000430  f4 a4 90 5c 02 00 ff ff  53 ef 01 00 01 00 00 00  |...\....S.......|
>
>     After the 3rd boot:
>
>         root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
>         Mount count:              3
>
>         root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
>         00000430  63 a6 90 5c 03 00 ff ff  53 ef 01 00 01 00 00 00  |c..\....S.......|
>
> BTW, the values of "Last mount time", "Last write time" and "Lifetime writes" were also changed.
>
> I'm concerned that if the partition which is set to rdiffbase is changed as above,
> the binary delta update will be done correctly or not.

Well, technically it's just a patch, so if there is a difference in the
two partition images you diff, and be it the filesystem's mount count,
then this will end up in the patch and be applied on the device. If
that's deemed incorrect, then such filesystem metadata has to be
excluded from the diff by means of preprocessing both partition images
so that there's no difference in the metadata that could end up in the
binary patch.

The resulting partition's data is copied from the partition designated
by rdiffbase except for the patch contents that overrule these. So, to
stay in the above example, if the filesystem's mount count is not in the
binary patch, it's taken from rdiffbase.


> > > BTW, the warning message after binary delta update was as follows:
> > >
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm init: deleted inode referenced: 5040
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm init: deleted inode referenced: 5040
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> > >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> > comm mount: deleted inode referenced: 5833
> >
> > Well, my suspicion is that, after a delta-update of the partition, the
> > filesystem's metadata is corrupt, i.e., the metdata was partially
> > updated by a delta update, resulting in an inconsistent overall state.
> > Could you elaborate on the exact steps you performed? Is the diff done
> > from/to the right sources? Could as well be that the journal hasn't
> > committed the changes... Just a wild guess though...
> The exact steps I performed are as follows:
>
>      1. Build rootfs image as v1 by poky by reference to the following article:
>         <https://mkrak.org/2018/01/26/updating-embedded-linux-devices-part2/>
>      2. Boot BeagleBone Black (BBB) from microSD
>      3. Write "core-image-full-cmdline-beaglebone.wic" to /dev/mmcblk1 (eMMC) on BBB
>      4. Write "core-image-full-cmdline-beaglebone.ext4" to /dev/mmcblk1p2
>      5. Make /dev/mmcblk1p3 partition by fdisk and copy /dev/mmcblk1p2 to /dev/mmcblk1p3
>      6. Shutdown BBB and boot from /dev/mmcblk1p3
>      7. Add a change to the recipe of poky and rebuild rootfs image as v2
>      8. Make a delta image from v1 and v2 by rdiff command
>      9. Make swu image from attached sw-description, emmcsetup.lua, and the delta image

Well, in the attached sw-description, you're using
						device = "/dev/mmcblk1p2";
						properties: {
							rdiffbase = ["/dev/mmcblk1p2"];
						};
for "copy1" and
						device = "/dev/mmcblk1p3";
						properties: {
							rdiffbase = ["/dev/mmcblk1p3"];
						};
for "copy2" which basically says use /dev/mmcblk1p{2,3} as rdiffbase
(i.e. copy source) *and* target, hence you're overwriting
/dev/mmcblk1p{2,3} with /dev/mmcblk1p{2,3} + binary patch applied.
If /dev/mmcblk1p{2,3} happens to be mounted, then you'll get the ext4
errors as you're overwriting a mounted filesystem on the block layer.

>     10. Access http://[IP address of BBB]:8080/ by Web browser and upload the above swu image
>         (After the update is finished, It reboots automatically)

Well, how did you instruct SWUpdate to choose "copy1" or "copy2"?
Can you provide the logs of the SWUpdate runs and the information from
which partition you booted while running SWUpdate?

>     11. Check the update is done correctly
>         (It boots from /dev/mmcblk1p2 and the rootfs image version is v2)

Well, I cannot tell about your setup but does
  value = "... setenv bootpart 1:3 ..." 
in "copy2" instruct to boot from /dev/mmcblk1p2? Same question applies to "copy1".

>     12. Do the step of No.10 to update the rootfs image on /dev/mmcblk1p3 to v2
>     13. After updating and rebooting, BBB is booted from /dev/mmcblk1p3 and
>         the rootfs image version is v2, but the ext4 warning message is shown
>
> If you need more detailed steps, please let me know.
>
> To tell the truth, at first, I set the different partition to "device" and "rdiffbase" field at sw-description.
> If "/dev/mmcblk1p2" was set to "device", I set "/dev/mmcblk1p3" to "rdiffbase" -- and vice versa.
> When I used this sw-description, the ext4 warning message was shown at the step of No.11.



Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-18 10:27         ` Christian Storm
@ 2019-03-22  5:01           ` akihiro27.suzuki at toshiba.co.jp
  2019-03-22 12:37             ` Christian Storm
  0 siblings, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-22  5:01 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

Sorry for the late reply.

> > I mounted rootfs with read-only.
> 
> OK, from the diffs it seems that temporary storage directories such as
> /run and /var/tmp are not separate mount points from your roots?
I built the rootfs image by poky with "read-only-rootfs" option like following URL.
<https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#creating-the-root-filesystem>

I think that the temporary storage directories were mounted as tmpfs as follows:

    root at beaglebone:~# df -T
    Filesystem     Type     1K-blocks  Used Available Use% Mounted on
    /dev/root      ext4        135221 75902     49409  61% /
    devtmpfs       devtmpfs    243420     0    243420   0% /dev
    tmpfs          tmpfs       252124   124    252000   1% /run
    tmpfs          tmpfs       252124   252    251872   1% /var/volatile

    root at beaglebone:~# mount
    /dev/mmcblk1p2 on / type ext4 (ro,relatime,data=ordered)
    devtmpfs on /dev type devtmpfs (rw,relatime,size=243420k,nr_inodes=60855,mode=755)
    proc on /proc type proc (rw,relatime)
    sysfs on /sys type sysfs (rw,relatime)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
    tmpfs on /var/volatile type tmpfs (rw,relatime)
    devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /var/lib type tmpfs (rw,relatime)

    root at beaglebone:~# ls -l /var
    total 4
    drwxr-xr-x  2 root root 1024 Feb 13 08:41 backups
    drwxr-xr-x  4 root root 1024 Mar 19 07:47 cache
    drwxr-xr-x 10 root root  220 Mar 19 08:20 lib
    drwxr-xr-x  2 root root 1024 Feb 13 08:41 local
    lrwxrwxrwx  1 root root    9 Mar 19 07:47 lock -> /run/lock
    lrwxrwxrwx  1 root root   17 Mar 19 07:47 log -> /var/volatile/log
    lrwxrwxrwx  1 root root    4 Mar 19 07:47 run -> /run
    drwxr-xr-x  4 root root 1024 Mar 19 07:47 spool
    lrwxrwxrwx  1 root root   17 Mar 19 07:47 tmp -> /var/volatile/tmp
    drwxrwxrwt  5 root root  100 Mar 19 08:20 volatile

> > I checked the difference of the rootfs image between before boot and
> after boot,
> > and at least the number of mounts had changed.
> >
> > I attached following log files. I think that 0x434 is a mount count.
> 
> You can use tune2fs -l /dev/<rootdevicenode> and look for
> "Mount count: <some number>" to verify this.
I checked this by tune2fs, and it was correct.

    After the 1st boot:

        root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
        Mount count:              1

        root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
        00000430  81 43 6d 38 01 00 ff ff  53 ef 01 00 01 00 00 00  |.Cm8....S.......|

    After the 2nd boot:

        root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
        Mount count:              2

        root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
        00000430  f4 a4 90 5c 02 00 ff ff  53 ef 01 00 01 00 00 00  |...\....S.......|

    After the 3rd boot:

        root at beaglebone:~# tune2fs -l /dev/mmcblk1p2 | grep "Mount count"
        Mount count:              3

        root at beaglebone:~# hexdump -C -n 2048 /dev/mmcblk1p2 | grep 430
        00000430  63 a6 90 5c 03 00 ff ff  53 ef 01 00 01 00 00 00  |c..\....S.......|

BTW, the values of "Last mount time", "Last write time" and "Lifetime writes" were also changed.

I'm concerned that if the partition which is set to rdiffbase is changed as above,
the binary delta update will be done correctly or not.

> Well, currently nothing written in code. But I can try to elaborate on
> it here:
> Assume that, initially, A/version=1 and B/version=1 is on-disk.
> Then, the delta artifact ART_1->2 := rdiff(version=1 -> version=2) is
> applied to B,
> resulting in A/version=1 and B/version=2 on-disk. Boot into B/version=2,
> which is
> assumably successful.
> Then, when wanting to update A to a version=3 by an artifact
> ART_2->3 := rdiff(version=2 -> version=3), first ART_1->2 has to be
> applied to A and
> thereafter ART_2->3 has to be applied to A.
Thank you for the detailed explanation. 
I was thinking the same way, too.

> > BTW, the warning message after binary delta update was as follows:
> >
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm init: deleted inode referenced: 5040
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm init: deleted inode referenced: 5040
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> 
> Well, my suspicion is that, after a delta-update of the partition, the
> filesystem's metadata is corrupt, i.e., the metdata was partially
> updated by a delta update, resulting in an inconsistent overall state.
> Could you elaborate on the exact steps you performed? Is the diff done
> from/to the right sources? Could as well be that the journal hasn't
> committed the changes... Just a wild guess though...
The exact steps I performed are as follows:

     1. Build rootfs image as v1 by poky by reference to the following article:
        <https://mkrak.org/2018/01/26/updating-embedded-linux-devices-part2/>
     2. Boot BeagleBone Black (BBB) from microSD
     3. Write "core-image-full-cmdline-beaglebone.wic" to /dev/mmcblk1 (eMMC) on BBB
     4. Write "core-image-full-cmdline-beaglebone.ext4" to /dev/mmcblk1p2
     5. Make /dev/mmcblk1p3 partition by fdisk and copy /dev/mmcblk1p2 to /dev/mmcblk1p3
     6. Shutdown BBB and boot from /dev/mmcblk1p3
     7. Add a change to the recipe of poky and rebuild rootfs image as v2
     8. Make a delta image from v1 and v2 by rdiff command
     9. Make swu image from attached sw-description, emmcsetup.lua, and the delta image
    10. Access http://[IP address of BBB]:8080/ by Web browser and upload the above swu image
        (After the update is finished, It reboots automatically)
    11. Check the update is done correctly
        (It boots from /dev/mmcblk1p2 and the rootfs image version is v2)
    12. Do the step of No.10 to update the rootfs image on /dev/mmcblk1p3 to v2
    13. After updating and rebooting, BBB is booted from /dev/mmcblk1p3 and
        the rootfs image version is v2, but the ext4 warning message is shown

If you need more detailed steps, please let me know.

To tell the truth, at first, I set the different partition to "device" and "rdiffbase" field at sw-description.
If "/dev/mmcblk1p2" was set to "device", I set "/dev/mmcblk1p3" to "rdiffbase" -- and vice versa.
When I used this sw-description, the ext4 warning message was shown at the step of No.11.

> What kernel version are you using? There are some issues with v4.19.3
> and v4.19.4 and ext4 filesystems having the same symptoms...
The kernel version is v4.12.28, but I think that it is no relation of this issue...

    root at beaglebone:~# uname -a
    Linux beaglebone 4.12.28-yocto-standard #1 PREEMPT Wed Feb 13 09:33:37 UTC 2019 armv7l armv7l armv7l GNU/Linux

Best regards,
Suzuki

> -----Original Message-----
> From: Christian Storm [mailto:christian.storm at siemens.com]
> Sent: Monday, March 18, 2019 7:28 PM
> To: cip-dev at lists.cip-project.org
> Cc: suzuki akihiro(???? ???? ????????????????)
> <akihiro27.suzuki@toshiba.co.jp>; jan.kiszka at siemens.com;
> SZ.Lin at moxa.com
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Suzuki,
> 
> > > > > [Note] we are planning to develop the SWUpdate demo using ISAR,
> any
> > > > > advice or news about how to build SWUpdate on ISAR with the right
> > > > > U-Boot environment?
> > > > >
> > > > > - Regarding SWUpdate we hit an issue that we had not expected
> > > > > before. Suzuki-san was trying to update the standard BBB debian
> > > > > image (or a yocto-made one), but there were many warnings about
> > > > > orphan nodes etc. After some investigation the reason seems to
> be
> > > > > that the rootfs is modified during the first boot (or something
> like
> > > > > that). This is probably one of the biggest problems with updating
> > > > > images instead of files.
> > > >
> > > > Christian, any remarks?
> > >
> > > Hm, did you check that you didn't flash the filesystem you have
> > > currently booted, i.e., are you overwriting the currently running
> > > root filesystem? I have seen such errors when I did this by accident.
> >
> > I mounted rootfs with read-only.
> 
> OK, from the diffs it seems that temporary storage directories such as
> /run and /var/tmp are not separate mount points from your roots?
> 
> > I checked the difference of the rootfs image between before boot and
> after boot,
> > and at least the number of mounts had changed.
> >
> > I attached following log files. I think that 0x434 is a mount count.
> 
> You can use tune2fs -l /dev/<rootdevicenode> and look for
> "Mount count: <some number>" to verify this.
> 
> >
> >     mmcblk1p2-1-2.diff: The difference of rootfs image between 1st boot
> and 2nd boot
> >     mmcblk1p2-2-3.diff: The difference of rootfs image between 2nd boot
> and 3rd boot
> >
> > Do you have some example of A/B update with binary delta update?
> 
> Well, currently nothing written in code. But I can try to elaborate on
> it here:
> Assume that, initially, A/version=1 and B/version=1 is on-disk.
> Then, the delta artifact ART_1->2 := rdiff(version=1 -> version=2) is
> applied to B,
> resulting in A/version=1 and B/version=2 on-disk. Boot into B/version=2,
> which is
> assumably successful.
> Then, when wanting to update A to a version=3 by an artifact
> ART_2->3 := rdiff(version=2 -> version=3), first ART_1->2 has to be
> applied to A and
> thereafter ART_2->3 has to be applied to A.
> 
> Thing is here, you may have to apply a sequence of delta updates to the
> "other" partition so that applying the latest delta to it results in a
> consistent state, i.e., you have to do a "catchup" so that it matches
> the version the latest diff is done against.
> 
> That said, in order to not be forced to store ART_1->2 on the device,
> you can apply ART_1->2 to A once successfully booted into B/version=2.
> Or you can generate and apply ART_1->3 := rdiff(version=1 -> version=3)
> to A.
> Or you can split the update into first downloading and applying ART_1->2
> and the ART_2->3. There are many options, actually, depending on your
> preferences....
> 
> 
> > BTW, the warning message after binary delta update was as follows:
> >
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm init: deleted inode referenced: 5040
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm init: deleted inode referenced: 5040
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> >     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12:
> comm mount: deleted inode referenced: 5833
> 
> Well, my suspicion is that, after a delta-update of the partition, the
> filesystem's metadata is corrupt, i.e., the metdata was partially
> updated by a delta update, resulting in an inconsistent overall state.
> Could you elaborate on the exact steps you performed? Is the diff done
> from/to the right sources? Could as well be that the journal hasn't
> committed the changes... Just a wild guess though...
> 
> What kernel version are you using? There are some issues with v4.19.3
> and v4.19.4 and ext4 filesystems having the same symptoms...
> 
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M??nchen, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sw-description
Type: application/octet-stream
Size: 1178 bytes
Desc: sw-description
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190322/e3b6a710/attachment-0001.obj>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-03-21  0:48 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-03-21  0:48 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Welcome our new kernel maintainer ? Pavel!

* AI review
#action Please send configuration file of kernel 4.19 to cip-dev before end of March.
#action Daniel has to upload to the wiki the SW updates tool comparison document?(https://irclogs.baserock.org/meetings/cip/2019/03/cip.2019-03-14-09.00.log.html#l-89, 09:23:00)
#action Mae please add a link to the SW updates wiki page from the embedded world CIP release page?(https://irclogs.baserock.org/meetings/cip/2019/03/cip.2019-03-14-09.00.log.html#l-90, 09:23:02)

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update
* 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.

I might not be able to attend this meeting since I'm OOO today, Gavin will chair today's meeting.

Best regards,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-18  9:14       ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-18 10:27         ` Christian Storm
  2019-03-22  5:01           ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: Christian Storm @ 2019-03-18 10:27 UTC (permalink / raw)
  To: cip-dev

Hi Suzuki,

> > > > [Note] we are planning to develop the SWUpdate demo using ISAR, any
> > > > advice or news about how to build SWUpdate on ISAR with the right
> > > > U-Boot environment?
> > > >
> > > > - Regarding SWUpdate we hit an issue that we had not expected
> > > > before. Suzuki-san was trying to update the standard BBB debian
> > > > image (or a yocto-made one), but there were many warnings about
> > > > orphan nodes etc. After some investigation the reason seems to be
> > > > that the rootfs is modified during the first boot (or something like
> > > > that). This is probably one of the biggest problems with updating
> > > > images instead of files.
> > >
> > > Christian, any remarks?
> > 
> > Hm, did you check that you didn't flash the filesystem you have
> > currently booted, i.e., are you overwriting the currently running
> > root filesystem? I have seen such errors when I did this by accident.
>
> I mounted rootfs with read-only.

OK, from the diffs it seems that temporary storage directories such as
/run and /var/tmp are not separate mount points from your roots?

> I checked the difference of the rootfs image between before boot and after boot,
> and at least the number of mounts had changed.
> 
> I attached following log files. I think that 0x434 is a mount count.

You can use tune2fs -l /dev/<rootdevicenode> and look for
"Mount count: <some number>" to verify this.

> 
>     mmcblk1p2-1-2.diff: The difference of rootfs image between 1st boot and 2nd boot
>     mmcblk1p2-2-3.diff: The difference of rootfs image between 2nd boot and 3rd boot
> 
> Do you have some example of A/B update with binary delta update?

Well, currently nothing written in code. But I can try to elaborate on it here:
Assume that, initially, A/version=1 and B/version=1 is on-disk.
Then, the delta artifact ART_1->2 := rdiff(version=1 -> version=2) is applied to B,
resulting in A/version=1 and B/version=2 on-disk. Boot into B/version=2, which is
assumably successful.
Then, when wanting to update A to a version=3 by an artifact
ART_2->3 := rdiff(version=2 -> version=3), first ART_1->2 has to be applied to A and
thereafter ART_2->3 has to be applied to A.

Thing is here, you may have to apply a sequence of delta updates to the
"other" partition so that applying the latest delta to it results in a
consistent state, i.e., you have to do a "catchup" so that it matches
the version the latest diff is done against.

That said, in order to not be forced to store ART_1->2 on the device,
you can apply ART_1->2 to A once successfully booted into B/version=2.
Or you can generate and apply ART_1->3 := rdiff(version=1 -> version=3) to A.
Or you can split the update into first downloading and applying ART_1->2
and the ART_2->3. There are many options, actually, depending on your
preferences....


> BTW, the warning message after binary delta update was as follows:
> 
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm init: deleted inode referenced: 5040
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm init: deleted inode referenced: 5040
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
>     EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833

Well, my suspicion is that, after a delta-update of the partition, the
filesystem's metadata is corrupt, i.e., the metdata was partially
updated by a delta update, resulting in an inconsistent overall state.
Could you elaborate on the exact steps you performed? Is the diff done
from/to the right sources? Could as well be that the journal hasn't
committed the changes... Just a wild guess though...

What kernel version are you using? There are some issues with v4.19.3
and v4.19.4 and ext4 filesystems having the same symptoms...


Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-18  8:42     ` Christian Storm
@ 2019-03-18  9:14       ` akihiro27.suzuki at toshiba.co.jp
  2019-03-18 10:27         ` Christian Storm
  0 siblings, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-18  9:14 UTC (permalink / raw)
  To: cip-dev

Hi Christian,

> > > [Note] we are planning to develop the SWUpdate demo using ISAR, any
> > > advice or news about how to build SWUpdate on ISAR with the right
> > > U-Boot environment?
> > >
> > > - Regarding SWUpdate we hit an issue that we had not expected
> > > before. Suzuki-san was trying to update the standard BBB debian
> > > image (or a yocto-made one), but there were many warnings about
> > > orphan nodes etc. After some investigation the reason seems to be
> > > that the rootfs is modified during the first boot (or something like
> > > that). This is probably one of the biggest problems with updating
> > > images instead of files.
> >
> > Christian, any remarks?
> 
> Hm, did you check that you didn't flash the filesystem you have
> currently booted, i.e., are you overwriting the currently running
> root filesystem? I have seen such errors when I did this by accident.
I mounted rootfs with read-only.
I checked the difference of the rootfs image between before boot and after boot,
and at least the number of mounts had changed.

I attached following log files. I think that 0x434 is a mount count.

    mmcblk1p2-1-2.diff: The difference of rootfs image between 1st boot and 2nd boot
    mmcblk1p2-2-3.diff: The difference of rootfs image between 2nd boot and 3rd boot

Do you have some example of A/B update with binary delta update?

BTW, the warning message after binary delta update was as follows:

    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm init: deleted inode referenced: 5040
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm init: deleted inode referenced: 5040
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833
    EXT4-fs error (device mmcblk1p3): ext4_lookup:1584: inode #12: comm mount: deleted inode referenced: 5833

Best regards,
Suzuki


> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Christian
> Storm
> Sent: Monday, March 18, 2019 5:42 PM
> To: Jan Kiszka <jan.kiszka@siemens.com>
> Cc: SZ.Lin at moxa.com; cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> Hi,
> 
> > > [Note] we are planning to develop the SWUpdate demo using ISAR, any
> > > advice or news about how to build SWUpdate on ISAR with the right
> > > U-Boot environment?
> > >
> > > - Regarding SWUpdate we hit an issue that we had not expected
> > > before. Suzuki-san was trying to update the standard BBB debian
> > > image (or a yocto-made one), but there were many warnings about
> > > orphan nodes etc. After some investigation the reason seems to be
> > > that the rootfs is modified during the first boot (or something like
> > > that). This is probably one of the biggest problems with updating
> > > images instead of files.
> >
> > Christian, any remarks?
> 
> Hm, did you check that you didn't flash the filesystem you have
> currently booted, i.e., are you overwriting the currently running
> root filesystem? I have seen such errors when I did this by accident.
> 
> Kind regards,
>    Christian
> 
> --
> Dr. Christian Storm
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Otto-Hahn-Ring 6, 81739 M?nchen, Germany
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mmcblk1p2-1-2.diff
Type: application/octet-stream
Size: 20959 bytes
Desc: mmcblk1p2-1-2.diff
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190318/96c49ba5/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mmcblk1p2-2-3.diff
Type: application/octet-stream
Size: 7953 bytes
Desc: mmcblk1p2-2-3.diff
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190318/96c49ba5/attachment-0003.obj>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-15  9:24   ` Jan Kiszka
  2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-18  8:42     ` Christian Storm
  2019-03-18  9:14       ` akihiro27.suzuki at toshiba.co.jp
  1 sibling, 1 reply; 195+ messages in thread
From: Christian Storm @ 2019-03-18  8:42 UTC (permalink / raw)
  To: cip-dev

Hi,

> > [Note] we are planning to develop the SWUpdate demo using ISAR, any
> > advice or news about how to build SWUpdate on ISAR with the right
> > U-Boot environment?
> > 
> > - Regarding SWUpdate we hit an issue that we had not expected
> > before. Suzuki-san was trying to update the standard BBB debian
> > image (or a yocto-made one), but there were many warnings about
> > orphan nodes etc. After some investigation the reason seems to be
> > that the rootfs is modified during the first boot (or something like
> > that). This is probably one of the biggest problems with updating
> > images instead of files.
> 
> Christian, any remarks?

Hm, did you check that you didn't flash the filesystem you have
currently booted, i.e., are you overwriting the currently running
root filesystem? I have seen such errors when I did this by accident.

Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Otto-Hahn-Ring 6, 81739 M?nchen, Germany

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-15 10:50       ` Jan Kiszka
  2019-03-18  1:42         ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-18  2:53         ` akihiro27.suzuki at toshiba.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-18  2:53 UTC (permalink / raw)
  To: cip-dev

>     $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml
I made a mistake. We don't need sudo to run kas-docker.

Suzuki

> -----Original Message-----
> From: suzuki akihiro(?? ?? ????????)
> Sent: Monday, March 18, 2019 10:42 AM
> To: Jan Kiszka <jan.kiszka@siemens.com>; sangorrin daniel(????? ?
> ??? ????????) <daniel.sangorrin@toshiba.co.jp>;
> SZ.Lin at moxa.com; cip-dev at lists.cip-project.org;
> christian.storm at siemens.com
> Subject: RE: [cip-dev] CIP IRC weekly meeting today
> 
> Hi Jan,
> 
> > Were you building natively on Debian or inside the kas container?
> I was executing following commands according to the README.md at
> isar-cip-core,
> so I think I was building inside the kas container.
> 
>     $ wget
> https://raw.githubusercontent.com/siemens/kas/master/kas-docker
>     $ chmod a+x kas-docker
>     $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml
> 
> The error is as follows (from log.do_bootstrap of isar-bootstrap-target):
> 
>     DEBUG: Executing shell function do_bootstrap
>     I: Running command: debootstrap --arch armhf --foreign --verbose
> --variant=minbase --include=locales
> --components=main,contrib,non-free stretch
> /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs
> http://ftp.de.debian.org/debian
>     I: Retrieving InRelease
>     I: Retrieving Release
>     I: Retrieving Release.gpg
>     I: Checking Release signature
>     I: Valid Release signature (key id
> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
>     I: Retrieving Packages
>     I: Validating Packages
>     I: Retrieving Packages
>     I: Validating Packages
>     I: Retrieving Packages
>     I: Validating Packages
>     I: Resolving dependencies of required packages...
>     I: Resolving dependencies of base packages...
>     I: Found additional required dependencies: libaudit1
> libaudit-common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0
> libgcrypt20 libgpg-error0 liblz4-1 libncursesw5 libsemanage1
> libsemanage-common libsystemd0 libudev1 libustr-1.0-1
>     I: Found additional base dependencies: adduser
> debian-archive-keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6
>     I: Checking component main on http://ftp.de.debian.org/debian...
>     I: Retrieving libacl1 2.2.52-3+b1
>     I: Validating libacl1 2.2.52-3+b1
>     I: Retrieving adduser 3.115
>     I: Validating adduser 3.115
>     I: Retrieving apt 1.4.9
>     I: Validating apt 1.4.9
>     I: Retrieving libapt-pkg5.0 1.4.9
>     I: Validating libapt-pkg5.0 1.4.9
>     I: Retrieving libattr1 1:2.4.47-2+b2
>     I: Validating libattr1 1:2.4.47-2+b2
>     I: Retrieving libaudit-common 1:2.6.7-2
>     I: Validating libaudit-common 1:2.6.7-2
>     I: Retrieving libaudit1 1:2.6.7-2
>     I: Validating libaudit1 1:2.6.7-2
>     I: Retrieving base-files 9.9+deb9u8
>     I: Validating base-files 9.9+deb9u8
>     I: Retrieving base-passwd 3.5.43
>     I: Validating base-passwd 3.5.43
>     I: Retrieving bash 4.4-5
>     I: Validating bash 4.4-5
>     I: Retrieving libbz2-1.0 1.0.6-8.1
>     I: Validating libbz2-1.0 1.0.6-8.1
>     I: Retrieving libdebconfclient0 0.227
>     I: Validating libdebconfclient0 0.227
>     I: Retrieving coreutils 8.26-3
>     I: Validating coreutils 8.26-3
>     I: Retrieving dash 0.5.8-2.4
>     I: Validating dash 0.5.8-2.4
>     I: Retrieving libdb5.3 5.3.28-12+deb9u1
>     I: Validating libdb5.3 5.3.28-12+deb9u1
>     I: Retrieving debconf 1.5.61
>     I: Validating debconf 1.5.61
>     I: Retrieving debian-archive-keyring 2017.5
>     I: Validating debian-archive-keyring 2017.5
>     I: Retrieving debianutils 4.8.1.1
>     I: Validating debianutils 4.8.1.1
>     I: Retrieving diffutils 1:3.5-3
>     I: Validating diffutils 1:3.5-3
>     I: Retrieving dpkg 1.18.25
>     I: Validating dpkg 1.18.25
>     I: Retrieving e2fslibs 1.43.4-2
>     I: Validating e2fslibs 1.43.4-2
>     I: Retrieving e2fsprogs 1.43.4-2
>     I: Validating e2fsprogs 1.43.4-2
>     I: Retrieving libcomerr2 1.43.4-2
>     I: Validating libcomerr2 1.43.4-2
>     I: Retrieving libss2 1.43.4-2
>     I: Validating libss2 1.43.4-2
>     I: Retrieving findutils 4.6.0+git+20161106-2
>     I: Validating findutils 4.6.0+git+20161106-2
>     I: Retrieving gcc-6-base 6.3.0-18+deb9u1
>     I: Validating gcc-6-base 6.3.0-18+deb9u1
>     I: Retrieving libgcc1 1:6.3.0-18+deb9u1
>     I: Validating libgcc1 1:6.3.0-18+deb9u1
>     I: Retrieving libstdc++6 6.3.0-18+deb9u1
>     I: Validating libstdc++6 6.3.0-18+deb9u1
>     I: Retrieving libc-bin 2.24-11+deb9u4
>     I: Validating libc-bin 2.24-11+deb9u4
>     I: Retrieving libc-l10n 2.24-11+deb9u4
>     I: Validating libc-l10n 2.24-11+deb9u4
>     I: Retrieving libc6 2.24-11+deb9u4
>     I: Validating libc6 2.24-11+deb9u4
>     I: Retrieving locales 2.24-11+deb9u4
>     I: Validating locales 2.24-11+deb9u4
>     I: Retrieving multiarch-support 2.24-11+deb9u4
>     I: Validating multiarch-support 2.24-11+deb9u4
>     I: Retrieving gpgv 2.1.18-8~deb9u4
>     I: Validating gpgv 2.1.18-8~deb9u4
>     I: Retrieving grep 2.27-2
>     I: Validating grep 2.27-2
>     I: Retrieving gzip 1.6-5+b1
>     I: Validating gzip 1.6-5+b1
>     I: Retrieving hostname 3.18+b1
>     I: Validating hostname 3.18+b1
>     I: Retrieving init-system-helpers 1.48
>     I: Validating init-system-helpers 1.48
>     I: Retrieving libcap-ng0 0.7.7-3+b1
>     I: Validating libcap-ng0 0.7.7-3+b1
>     I: Retrieving libgcrypt20 1.7.6-2+deb9u3
>     I: Validating libgcrypt20 1.7.6-2+deb9u3
>     I: Retrieving libgpg-error0 1.26-2
>     I: Validating libgpg-error0 1.26-2
>     I: Retrieving libselinux1 2.6-3+b3
>     I: Validating libselinux1 2.6-3+b3
>     I: Retrieving libsemanage-common 2.6-2
>     I: Validating libsemanage-common 2.6-2
>     I: Retrieving libsemanage1 2.6-2
>     I: Validating libsemanage1 2.6-2
>     I: Retrieving libsepol1 2.6-2
>     I: Validating libsepol1 2.6-2
>     I: Retrieving lsb-base 9.20161125
>     I: Validating lsb-base 9.20161125
>     I: Retrieving liblz4-1 0.0~r131-2+b1
>     I: Validating liblz4-1 0.0~r131-2+b1
>     I: Retrieving mawk 1.3.3-17+b3
>     I: Validating mawk 1.3.3-17+b3
>     I: Retrieving libncursesw5 6.0+20161126-1+deb9u2
>     I: Validating libncursesw5 6.0+20161126-1+deb9u2
>     I: Retrieving libtinfo5 6.0+20161126-1+deb9u2
>     I: Validating libtinfo5 6.0+20161126-1+deb9u2
>     I: Retrieving ncurses-base 6.0+20161126-1+deb9u2
>     I: Validating ncurses-base 6.0+20161126-1+deb9u2
>     I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2
>     I: Validating ncurses-bin 6.0+20161126-1+deb9u2
>     I: Retrieving libpam-modules 1.1.8-3.6
>     I: Validating libpam-modules 1.1.8-3.6
>     I: Retrieving libpam-modules-bin 1.1.8-3.6
>     I: Validating libpam-modules-bin 1.1.8-3.6
>     I: Retrieving libpam-runtime 1.1.8-3.6
>     I: Validating libpam-runtime 1.1.8-3.6
>     I: Retrieving libpam0g 1.1.8-3.6
>     I: Validating libpam0g 1.1.8-3.6
>     I: Retrieving libpcre3 2:8.39-3
>     I: Validating libpcre3 2:8.39-3
>     I: Retrieving perl-base 5.24.1-3+deb9u5
>     I: Validating perl-base 5.24.1-3+deb9u5
>     I: Retrieving sed 4.4-1
>     I: Validating sed 4.4-1
>     I: Retrieving sensible-utils 0.0.9+deb9u1
>     I: Validating sensible-utils 0.0.9+deb9u1
>     I: Retrieving login 1:4.4-4.1
>     I: Validating login 1:4.4-4.1
>     I: Retrieving passwd 1:4.4-4.1
>     I: Validating passwd 1:4.4-4.1
>     I: Retrieving libsystemd0 232-25+deb9u8
>     I: Validating libsystemd0 232-25+deb9u8
>     I: Retrieving libudev1 232-25+deb9u8
>     I: Validating libudev1 232-25+deb9u8
>     I: Retrieving sysvinit-utils 2.88dsf-59.9
>     I: Validating sysvinit-utils 2.88dsf-59.9
>     I: Retrieving tar 1.29b-1.1
>     I: Validating tar 1.29b-1.1
>     I: Retrieving tzdata 2018i-0+deb9u1
>     I: Validating tzdata 2018i-0+deb9u1
>     I: Retrieving libustr-1.0-1 1.0.4-6
>     I: Validating libustr-1.0-1 1.0.4-6
>     I: Retrieving bsdutils 1:2.29.2-1+deb9u1
>     I: Validating bsdutils 1:2.29.2-1+deb9u1
>     I: Retrieving libblkid1 2.29.2-1+deb9u1
>     I: Validating libblkid1 2.29.2-1+deb9u1
>     I: Retrieving libfdisk1 2.29.2-1+deb9u1
>     I: Validating libfdisk1 2.29.2-1+deb9u1
>     I: Retrieving libmount1 2.29.2-1+deb9u1
>     I: Validating libmount1 2.29.2-1+deb9u1
>     I: Retrieving libsmartcols1 2.29.2-1+deb9u1
>     I: Validating libsmartcols1 2.29.2-1+deb9u1
>     I: Retrieving libuuid1 2.29.2-1+deb9u1
>     I: Validating libuuid1 2.29.2-1+deb9u1
>     I: Retrieving mount 2.29.2-1+deb9u1
>     I: Validating mount 2.29.2-1+deb9u1
>     I: Retrieving util-linux 2.29.2-1+deb9u1
>     I: Validating util-linux 2.29.2-1+deb9u1
>     I: Retrieving liblzma5 5.2.2-1.2+b1
>     I: Validating liblzma5 5.2.2-1.2+b1
>     I: Retrieving zlib1g 1:1.2.8.dfsg-5
>     I: Validating zlib1g 1:1.2.8.dfsg-5
>     I: Chosen extractor for .deb packages: dpkg-deb
>     I: Extracting libacl1...
>     I: Extracting libattr1...
>     I: Extracting libaudit-common...
>     I: Extracting libaudit1...
>     I: Extracting base-files...
>     I: Extracting base-passwd...
>     I: Extracting bash...
>     I: Extracting libbz2-1.0...
>     I: Extracting libdebconfclient0...
>     I: Extracting coreutils...
>     I: Extracting dash...
>     I: Extracting libdb5.3...
>     I: Extracting debconf...
>     I: Extracting debianutils...
>     I: Extracting diffutils...
>     I: Extracting dpkg...
>     I: Extracting e2fslibs...
>     I: Extracting e2fsprogs...
>     I: Extracting libcomerr2...
>     I: Extracting libss2...
>     I: Extracting findutils...
>     I: Extracting gcc-6-base...
>     I: Extracting libgcc1...
>     I: Extracting libc-bin...
>     I: Extracting libc6...
>     I: Extracting multiarch-support...
>     I: Extracting grep...
>     I: Extracting gzip...
>     I: Extracting hostname...
>     I: Extracting init-system-helpers...
>     I: Extracting libcap-ng0...
>     I: Extracting libgcrypt20...
>     I: Extracting libgpg-error0...
>     I: Extracting libselinux1...
>     I: Extracting libsemanage-common...
>     I: Extracting libsemanage1...
>     I: Extracting libsepol1...
>     I: Extracting lsb-base...
>     I: Extracting liblz4-1...
>     I: Extracting mawk...
>     I: Extracting libncursesw5...
>     I: Extracting libtinfo5...
>     I: Extracting ncurses-base...
>     I: Extracting ncurses-bin...
>     I: Extracting libpam-modules...
>     I: Extracting libpam-modules-bin...
>     I: Extracting libpam-runtime...
>     I: Extracting libpam0g...
>     I: Extracting libpcre3...
>     I: Extracting perl-base...
>     I: Extracting sed...
>     I: Extracting sensible-utils...
>     I: Extracting login...
>     I: Extracting passwd...
>     I: Extracting libsystemd0...
>     I: Extracting libudev1...
>     I: Extracting sysvinit-utils...
>     I: Extracting tar...
>     I: Extracting tzdata...
>     I: Extracting libustr-1.0-1...
>     I: Extracting bsdutils...
>     I: Extracting libblkid1...
>     I: Extracting libfdisk1...
>     I: Extracting libmount1...
>     I: Extracting libsmartcols1...
>     I: Extracting libuuid1...
>     I: Extracting mount...
>     I: Extracting util-linux...
>     I: Extracting liblzma5...
>     I: Extracting zlib1g...
>     I: Running command: chroot
> /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs
> /debootstrap/debootstrap --second-stage
>     chroot: failed to run command ?/debootstrap/debootstrap?: No such
> file or directory
>     WARNING: exit code 127 from a shell command.
>     ERROR: Function failed: do_bootstrap (log file is located at
> /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/temp/log.d
> o_bootstrap.316)
> 
> Best regards,
> Suzuki
> 
> 
> > -----Original Message-----
> > From: Jan Kiszka [mailto:jan.kiszka at siemens.com]
> > Sent: Friday, March 15, 2019 7:50 PM
> > To: suzuki akihiro(?? ?? ????????)
> > <akihiro27.suzuki@toshiba.co.jp>; sangorrin daniel(????? ??
> ?
> > ? ????????) <daniel.sangorrin@toshiba.co.jp>;
> > SZ.Lin at moxa.com; cip-dev at lists.cip-project.org;
> > christian.storm at siemens.com
> > Subject: Re: [cip-dev] CIP IRC weekly meeting today
> >
> > On 15.03.19 10:48, akihiro27.suzuki at toshiba.co.jp wrote:
> > > Hi Jan,
> > >
> > >> On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
> > >>> - Suzuki-san has found a couple of issues in ISAR CIP Core.
> > >>>     - when building ISAR for the beaglebone black it complains that
> > >> "/debootstrap/debootstrap is not found" (or something like that).
> He
> > will
> > >> post a new issue on the Gitlab web page with the complete log.
> > >>
> > >> Has this been resolved locally?
> > > When I tried to build isar-cip-core on another 2 machines, the error
> > didn't occur.
> > > So, my machine which occurred the error may have some problem.
> >
> > Were you building natively on Debian or inside the kas container?
> >
> > > I will check it when I have the time.
> >
> > OK, thanks.
> >
> > Jan
> >
> > --
> > Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> > Corporate Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-15 10:50       ` Jan Kiszka
@ 2019-03-18  1:42         ` akihiro27.suzuki at toshiba.co.jp
  2019-03-18  2:53         ` akihiro27.suzuki at toshiba.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-18  1:42 UTC (permalink / raw)
  To: cip-dev

Hi Jan,

> Were you building natively on Debian or inside the kas container?
I was executing following commands according to the README.md at isar-cip-core,
so I think I was building inside the kas container.

    $ wget https://raw.githubusercontent.com/siemens/kas/master/kas-docker
    $ chmod a+x kas-docker
    $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml

The error is as follows (from log.do_bootstrap of isar-bootstrap-target):

    DEBUG: Executing shell function do_bootstrap
    I: Running command: debootstrap --arch armhf --foreign --verbose --variant=minbase --include=locales --components=main,contrib,non-free stretch /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs http://ftp.de.debian.org/debian
    I: Retrieving InRelease 
    I: Retrieving Release 
    I: Retrieving Release.gpg 
    I: Checking Release signature
    I: Valid Release signature (key id 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
    I: Retrieving Packages 
    I: Validating Packages 
    I: Retrieving Packages 
    I: Validating Packages 
    I: Retrieving Packages 
    I: Validating Packages 
    I: Resolving dependencies of required packages...
    I: Resolving dependencies of base packages...
    I: Found additional required dependencies: libaudit1 libaudit-common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common libsystemd0 libudev1 libustr-1.0-1 
    I: Found additional base dependencies: adduser debian-archive-keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 
    I: Checking component main on http://ftp.de.debian.org/debian...
    I: Retrieving libacl1 2.2.52-3+b1
    I: Validating libacl1 2.2.52-3+b1
    I: Retrieving adduser 3.115
    I: Validating adduser 3.115
    I: Retrieving apt 1.4.9
    I: Validating apt 1.4.9
    I: Retrieving libapt-pkg5.0 1.4.9
    I: Validating libapt-pkg5.0 1.4.9
    I: Retrieving libattr1 1:2.4.47-2+b2
    I: Validating libattr1 1:2.4.47-2+b2
    I: Retrieving libaudit-common 1:2.6.7-2
    I: Validating libaudit-common 1:2.6.7-2
    I: Retrieving libaudit1 1:2.6.7-2
    I: Validating libaudit1 1:2.6.7-2
    I: Retrieving base-files 9.9+deb9u8
    I: Validating base-files 9.9+deb9u8
    I: Retrieving base-passwd 3.5.43
    I: Validating base-passwd 3.5.43
    I: Retrieving bash 4.4-5
    I: Validating bash 4.4-5
    I: Retrieving libbz2-1.0 1.0.6-8.1
    I: Validating libbz2-1.0 1.0.6-8.1
    I: Retrieving libdebconfclient0 0.227
    I: Validating libdebconfclient0 0.227
    I: Retrieving coreutils 8.26-3
    I: Validating coreutils 8.26-3
    I: Retrieving dash 0.5.8-2.4
    I: Validating dash 0.5.8-2.4
    I: Retrieving libdb5.3 5.3.28-12+deb9u1
    I: Validating libdb5.3 5.3.28-12+deb9u1
    I: Retrieving debconf 1.5.61
    I: Validating debconf 1.5.61
    I: Retrieving debian-archive-keyring 2017.5
    I: Validating debian-archive-keyring 2017.5
    I: Retrieving debianutils 4.8.1.1
    I: Validating debianutils 4.8.1.1
    I: Retrieving diffutils 1:3.5-3
    I: Validating diffutils 1:3.5-3
    I: Retrieving dpkg 1.18.25
    I: Validating dpkg 1.18.25
    I: Retrieving e2fslibs 1.43.4-2
    I: Validating e2fslibs 1.43.4-2
    I: Retrieving e2fsprogs 1.43.4-2
    I: Validating e2fsprogs 1.43.4-2
    I: Retrieving libcomerr2 1.43.4-2
    I: Validating libcomerr2 1.43.4-2
    I: Retrieving libss2 1.43.4-2
    I: Validating libss2 1.43.4-2
    I: Retrieving findutils 4.6.0+git+20161106-2
    I: Validating findutils 4.6.0+git+20161106-2
    I: Retrieving gcc-6-base 6.3.0-18+deb9u1
    I: Validating gcc-6-base 6.3.0-18+deb9u1
    I: Retrieving libgcc1 1:6.3.0-18+deb9u1
    I: Validating libgcc1 1:6.3.0-18+deb9u1
    I: Retrieving libstdc++6 6.3.0-18+deb9u1
    I: Validating libstdc++6 6.3.0-18+deb9u1
    I: Retrieving libc-bin 2.24-11+deb9u4
    I: Validating libc-bin 2.24-11+deb9u4
    I: Retrieving libc-l10n 2.24-11+deb9u4
    I: Validating libc-l10n 2.24-11+deb9u4
    I: Retrieving libc6 2.24-11+deb9u4
    I: Validating libc6 2.24-11+deb9u4
    I: Retrieving locales 2.24-11+deb9u4
    I: Validating locales 2.24-11+deb9u4
    I: Retrieving multiarch-support 2.24-11+deb9u4
    I: Validating multiarch-support 2.24-11+deb9u4
    I: Retrieving gpgv 2.1.18-8~deb9u4
    I: Validating gpgv 2.1.18-8~deb9u4
    I: Retrieving grep 2.27-2
    I: Validating grep 2.27-2
    I: Retrieving gzip 1.6-5+b1
    I: Validating gzip 1.6-5+b1
    I: Retrieving hostname 3.18+b1
    I: Validating hostname 3.18+b1
    I: Retrieving init-system-helpers 1.48
    I: Validating init-system-helpers 1.48
    I: Retrieving libcap-ng0 0.7.7-3+b1
    I: Validating libcap-ng0 0.7.7-3+b1
    I: Retrieving libgcrypt20 1.7.6-2+deb9u3
    I: Validating libgcrypt20 1.7.6-2+deb9u3
    I: Retrieving libgpg-error0 1.26-2
    I: Validating libgpg-error0 1.26-2
    I: Retrieving libselinux1 2.6-3+b3
    I: Validating libselinux1 2.6-3+b3
    I: Retrieving libsemanage-common 2.6-2
    I: Validating libsemanage-common 2.6-2
    I: Retrieving libsemanage1 2.6-2
    I: Validating libsemanage1 2.6-2
    I: Retrieving libsepol1 2.6-2
    I: Validating libsepol1 2.6-2
    I: Retrieving lsb-base 9.20161125
    I: Validating lsb-base 9.20161125
    I: Retrieving liblz4-1 0.0~r131-2+b1
    I: Validating liblz4-1 0.0~r131-2+b1
    I: Retrieving mawk 1.3.3-17+b3
    I: Validating mawk 1.3.3-17+b3
    I: Retrieving libncursesw5 6.0+20161126-1+deb9u2
    I: Validating libncursesw5 6.0+20161126-1+deb9u2
    I: Retrieving libtinfo5 6.0+20161126-1+deb9u2
    I: Validating libtinfo5 6.0+20161126-1+deb9u2
    I: Retrieving ncurses-base 6.0+20161126-1+deb9u2
    I: Validating ncurses-base 6.0+20161126-1+deb9u2
    I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2
    I: Validating ncurses-bin 6.0+20161126-1+deb9u2
    I: Retrieving libpam-modules 1.1.8-3.6
    I: Validating libpam-modules 1.1.8-3.6
    I: Retrieving libpam-modules-bin 1.1.8-3.6
    I: Validating libpam-modules-bin 1.1.8-3.6
    I: Retrieving libpam-runtime 1.1.8-3.6
    I: Validating libpam-runtime 1.1.8-3.6
    I: Retrieving libpam0g 1.1.8-3.6
    I: Validating libpam0g 1.1.8-3.6
    I: Retrieving libpcre3 2:8.39-3
    I: Validating libpcre3 2:8.39-3
    I: Retrieving perl-base 5.24.1-3+deb9u5
    I: Validating perl-base 5.24.1-3+deb9u5
    I: Retrieving sed 4.4-1
    I: Validating sed 4.4-1
    I: Retrieving sensible-utils 0.0.9+deb9u1
    I: Validating sensible-utils 0.0.9+deb9u1
    I: Retrieving login 1:4.4-4.1
    I: Validating login 1:4.4-4.1
    I: Retrieving passwd 1:4.4-4.1
    I: Validating passwd 1:4.4-4.1
    I: Retrieving libsystemd0 232-25+deb9u8
    I: Validating libsystemd0 232-25+deb9u8
    I: Retrieving libudev1 232-25+deb9u8
    I: Validating libudev1 232-25+deb9u8
    I: Retrieving sysvinit-utils 2.88dsf-59.9
    I: Validating sysvinit-utils 2.88dsf-59.9
    I: Retrieving tar 1.29b-1.1
    I: Validating tar 1.29b-1.1
    I: Retrieving tzdata 2018i-0+deb9u1
    I: Validating tzdata 2018i-0+deb9u1
    I: Retrieving libustr-1.0-1 1.0.4-6
    I: Validating libustr-1.0-1 1.0.4-6
    I: Retrieving bsdutils 1:2.29.2-1+deb9u1
    I: Validating bsdutils 1:2.29.2-1+deb9u1
    I: Retrieving libblkid1 2.29.2-1+deb9u1
    I: Validating libblkid1 2.29.2-1+deb9u1
    I: Retrieving libfdisk1 2.29.2-1+deb9u1
    I: Validating libfdisk1 2.29.2-1+deb9u1
    I: Retrieving libmount1 2.29.2-1+deb9u1
    I: Validating libmount1 2.29.2-1+deb9u1
    I: Retrieving libsmartcols1 2.29.2-1+deb9u1
    I: Validating libsmartcols1 2.29.2-1+deb9u1
    I: Retrieving libuuid1 2.29.2-1+deb9u1
    I: Validating libuuid1 2.29.2-1+deb9u1
    I: Retrieving mount 2.29.2-1+deb9u1
    I: Validating mount 2.29.2-1+deb9u1
    I: Retrieving util-linux 2.29.2-1+deb9u1
    I: Validating util-linux 2.29.2-1+deb9u1
    I: Retrieving liblzma5 5.2.2-1.2+b1
    I: Validating liblzma5 5.2.2-1.2+b1
    I: Retrieving zlib1g 1:1.2.8.dfsg-5
    I: Validating zlib1g 1:1.2.8.dfsg-5
    I: Chosen extractor for .deb packages: dpkg-deb
    I: Extracting libacl1...
    I: Extracting libattr1...
    I: Extracting libaudit-common...
    I: Extracting libaudit1...
    I: Extracting base-files...
    I: Extracting base-passwd...
    I: Extracting bash...
    I: Extracting libbz2-1.0...
    I: Extracting libdebconfclient0...
    I: Extracting coreutils...
    I: Extracting dash...
    I: Extracting libdb5.3...
    I: Extracting debconf...
    I: Extracting debianutils...
    I: Extracting diffutils...
    I: Extracting dpkg...
    I: Extracting e2fslibs...
    I: Extracting e2fsprogs...
    I: Extracting libcomerr2...
    I: Extracting libss2...
    I: Extracting findutils...
    I: Extracting gcc-6-base...
    I: Extracting libgcc1...
    I: Extracting libc-bin...
    I: Extracting libc6...
    I: Extracting multiarch-support...
    I: Extracting grep...
    I: Extracting gzip...
    I: Extracting hostname...
    I: Extracting init-system-helpers...
    I: Extracting libcap-ng0...
    I: Extracting libgcrypt20...
    I: Extracting libgpg-error0...
    I: Extracting libselinux1...
    I: Extracting libsemanage-common...
    I: Extracting libsemanage1...
    I: Extracting libsepol1...
    I: Extracting lsb-base...
    I: Extracting liblz4-1...
    I: Extracting mawk...
    I: Extracting libncursesw5...
    I: Extracting libtinfo5...
    I: Extracting ncurses-base...
    I: Extracting ncurses-bin...
    I: Extracting libpam-modules...
    I: Extracting libpam-modules-bin...
    I: Extracting libpam-runtime...
    I: Extracting libpam0g...
    I: Extracting libpcre3...
    I: Extracting perl-base...
    I: Extracting sed...
    I: Extracting sensible-utils...
    I: Extracting login...
    I: Extracting passwd...
    I: Extracting libsystemd0...
    I: Extracting libudev1...
    I: Extracting sysvinit-utils...
    I: Extracting tar...
    I: Extracting tzdata...
    I: Extracting libustr-1.0-1...
    I: Extracting bsdutils...
    I: Extracting libblkid1...
    I: Extracting libfdisk1...
    I: Extracting libmount1...
    I: Extracting libsmartcols1...
    I: Extracting libuuid1...
    I: Extracting mount...
    I: Extracting util-linux...
    I: Extracting liblzma5...
    I: Extracting zlib1g...
    I: Running command: chroot /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap --second-stage
    chroot: failed to run command ?/debootstrap/debootstrap?: No such file or directory
    WARNING: exit code 127 from a shell command.
    ERROR: Function failed: do_bootstrap (log file is located at /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/temp/log.do_bootstrap.316)

Best regards,
Suzuki


> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka at siemens.com]
> Sent: Friday, March 15, 2019 7:50 PM
> To: suzuki akihiro(?? ?? ????????)
> <akihiro27.suzuki@toshiba.co.jp>; sangorrin daniel(????? ???
> ? ????????) <daniel.sangorrin@toshiba.co.jp>;
> SZ.Lin at moxa.com; cip-dev at lists.cip-project.org;
> christian.storm at siemens.com
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> On 15.03.19 10:48, akihiro27.suzuki at toshiba.co.jp wrote:
> > Hi Jan,
> >
> >> On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
> >>> - Suzuki-san has found a couple of issues in ISAR CIP Core.
> >>>     - when building ISAR for the beaglebone black it complains that
> >> "/debootstrap/debootstrap is not found" (or something like that). He
> will
> >> post a new issue on the Gitlab web page with the complete log.
> >>
> >> Has this been resolved locally?
> > When I tried to build isar-cip-core on another 2 machines, the error
> didn't occur.
> > So, my machine which occurred the error may have some problem.
> 
> Were you building natively on Debian or inside the kas container?
> 
> > I will check it when I have the time.
> 
> OK, thanks.
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
@ 2019-03-15 10:50       ` Jan Kiszka
  2019-03-18  1:42         ` akihiro27.suzuki at toshiba.co.jp
  2019-03-18  2:53         ` akihiro27.suzuki at toshiba.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: Jan Kiszka @ 2019-03-15 10:50 UTC (permalink / raw)
  To: cip-dev

On 15.03.19 10:48, akihiro27.suzuki at toshiba.co.jp wrote:
> Hi Jan,
> 
>> On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
>>> - Suzuki-san has found a couple of issues in ISAR CIP Core.
>>>     - when building ISAR for the beaglebone black it complains that
>> "/debootstrap/debootstrap is not found" (or something like that). He will
>> post a new issue on the Gitlab web page with the complete log.
>>
>> Has this been resolved locally?
> When I tried to build isar-cip-core on another 2 machines, the error didn't occur.
> So, my machine which occurred the error may have some problem.

Were you building natively on Debian or inside the kas container?

> I will check it when I have the time.

OK, thanks.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-15  9:24   ` Jan Kiszka
@ 2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
  2019-03-15 10:50       ` Jan Kiszka
  2019-03-18  8:42     ` Christian Storm
  1 sibling, 1 reply; 195+ messages in thread
From: akihiro27.suzuki at toshiba.co.jp @ 2019-03-15  9:48 UTC (permalink / raw)
  To: cip-dev

Hi Jan,

> On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
> > - Suzuki-san has found a couple of issues in ISAR CIP Core.
> >    - when building ISAR for the beaglebone black it complains that
> "/debootstrap/debootstrap is not found" (or something like that). He will
> post a new issue on the Gitlab web page with the complete log.
> 
> Has this been resolved locally?
When I tried to build isar-cip-core on another 2 machines, the error didn't occur.
So, my machine which occurred the error may have some problem.
I will check it when I have the time.

Best regards,
Suzuki

---
Akihiro Suzuki
Corporate Software Engineering & Technology Center
Toshiba Corporation
Tel: +81-44-549-2476
E-mail: akihiro27.suzuki at toshiba.co.jp 

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Jan Kiszka
> Sent: Friday, March 15, 2019 6:24 PM
> To: sangorrin daniel(????? ???? ????????)
> <daniel.sangorrin@toshiba.co.jp>; SZ.Lin at moxa.com;
> cip-dev at lists.cip-project.org; Christian Storm
> <christian.storm@siemens.com>
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
> 
> On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
> > - Suzuki-san has found a couple of issues in ISAR CIP Core.
> >    - when building ISAR for the beaglebone black it complains that
> "/debootstrap/debootstrap is not found" (or something like that). He will
> post a new issue on the Gitlab web page with the complete log.
> 
> Has this been resolved locally?
> 
> >    - after building ISAR for qemu succesfully, he tried to run
> start-qemu.sh x86_64 and there was an issue with --nographics that
> required to add ttyS0 (or something like that) to the qemu parameters.
> He will be sending a patch soon.
> 
> Thanks, already commented.
> 
> > [Note] we are planning to develop the SWUpdate demo using ISAR, any
> advice or news about how to build SWUpdate on ISAR with the right U-Boot
> environment?
> >
> > - Regarding SWUpdate we hit an issue that we had not expected before.
> Suzuki-san was trying to update the standard BBB debian image (or a
> yocto-made one), but there were many warnings about orphan nodes etc.
> After some investigation the reason seems to be that the rootfs is modified
> during the first boot (or something like that). This is probably one of
> the biggest problems with updating images instead of files.
> 
> Christian, any remarks?
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
  2019-03-14  9:19   ` Chris Paterson
  2019-03-14  9:23   ` Patryk Mungai Ndungu
@ 2019-03-15  9:24   ` Jan Kiszka
  2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
  2019-03-18  8:42     ` Christian Storm
  2 siblings, 2 replies; 195+ messages in thread
From: Jan Kiszka @ 2019-03-15  9:24 UTC (permalink / raw)
  To: cip-dev

On 14.03.19 08:26, daniel.sangorrin at toshiba.co.jp wrote:
> - Suzuki-san has found a couple of issues in ISAR CIP Core.
>    - when building ISAR for the beaglebone black it complains that "/debootstrap/debootstrap is not found" (or something like that). He will post a new issue on the Gitlab web page with the complete log.

Has this been resolved locally?

>    - after building ISAR for qemu succesfully, he tried to run start-qemu.sh x86_64 and there was an issue with --nographics that required to add ttyS0 (or something like that) to the qemu parameters. He will be sending a patch soon.

Thanks, already commented.

> [Note] we are planning to develop the SWUpdate demo using ISAR, any advice or news about how to build SWUpdate on ISAR with the right U-Boot environment?
> 
> - Regarding SWUpdate we hit an issue that we had not expected before. Suzuki-san was trying to update the standard BBB debian image (or a yocto-made one), but there were many warnings about orphan nodes etc. After some investigation the reason seems to be that the rootfs is modified during the first boot (or something like that). This is probably one of the biggest problems with updating images instead of files.

Christian, any remarks?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
  2019-03-14  9:19   ` Chris Paterson
@ 2019-03-14  9:23   ` Patryk Mungai Ndungu
  2019-03-15  9:24   ` Jan Kiszka
  2 siblings, 0 replies; 195+ messages in thread
From: Patryk Mungai Ndungu @ 2019-03-14  9:23 UTC (permalink / raw)
  To: cip-dev

Hello Daniel,

> -----Original Message-----
> From: daniel.sangorrin at toshiba.co.jp <daniel.sangorrin@toshiba.co.jp>
> Sent: 14 March 2019 07:27
> To: SZ.Lin at moxa.com; cip-dev at lists.cip-project.org
> Cc: Patryk Mungai Ndungu <patryk.mungai-ndungu.kx@renesas.com>;
> akihiro27.suzuki at toshiba.co.jp; maemalynn at linuxfoundation.org
> Subject: RE: CIP IRC weekly meeting today
> 
> Hello SZ,
> 
> I can't attend today. I will write here a few updates
> 
> - I have added usbutils to CIP Core (Deby) for Patryk to use lsusb in his tests
>    - it seems to work fine now: https://lava.ciplatform.org/scheduler/job/725
>    - here is the YAML I used to test pwd, uname and lsusb. Anyone with an
> account can use it by clicking on "Resubmit" and optionally change the test:
> https://lava.ciplatform.org/scheduler/job/725/definition
> 

Thank you for adding lsusb. Sorry for not getting back to you earlier. I'll try running the integration tests I pushed the other week using the updated cip-core.

In terms of internal testing, these are the packages we add to our RFS Yocto build in order to run tests:

bonnie++ e2fsprogs-mke2fs alsa-utils pciutils ethtool i2c-tools util-linux procps libpng imagemagick


Kind Regards,
Patryk


> - Suzuki-san has found a couple of issues in ISAR CIP Core.
>   - when building ISAR for the beaglebone black it complains that
> "/debootstrap/debootstrap is not found" (or something like that). He will
> post a new issue on the Gitlab web page with the complete log.
>   - after building ISAR for qemu succesfully, he tried to run start-qemu.sh
> x86_64 and there was an issue with --nographics that required to add ttyS0
> (or something like that) to the qemu parameters. He will be sending a patch
> soon.
> [Note] we are planning to develop the SWUpdate demo using ISAR, any
> advice or news about how to build SWUpdate on ISAR with the right U-Boot
> environment?
> 
> - Regarding SWUpdate we hit an issue that we had not expected before.
> Suzuki-san was trying to update the standard BBB debian image (or a yocto-
> made one), but there were many warnings about orphan nodes etc. After
> some investigation the reason seems to be that the rootfs is modified during
> the first boot (or something like that). This is probably one of the biggest
> problems with updating images instead of files.
> 
> # Sorry for the "something like that"s, I have not verified by myself
> everything
> 
> #action I have to upload to the wiki the SW updates tool comparison
> document
> #action Mae please add a link to the SW updates wiki page from the
> embedded world CIP release page
> https://www.linuxfoundation.org/press-release/2019/02/civil-
> infrastructure-platform-announces-new-super-long-term-support-kernel-
> that-advances-automation-machine-learning-and-artificial-intelligence/
> 
> Thanks,
> Daniel
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-
> project.org> On Behalf Of SZ Lin (?
> > ??)
> > Sent: Thursday, March 14, 2019 10:55 AM
> > To: cip-dev at 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 IRC meeting was rescheduled to 18:00 (JST) starting from
> the first week of Nov. according to
> > F2F meeting discussion in ELCE.*
> >
> > US-West US-East? UK??? DE???? TW???? JP
> > 02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00
> >
> > Channel:
> > * irc:chat.freenode.net:6667/cip
> >
> > Agenda:
> >
> > * AI review
> > #action Iwamatsu-san will create a template page and send the link via
> mailing list afterward
> > #action Please send configuration file of kernel 4.19 to cip-dev before end
> of March.
> >
> > * Kernel maintenance updates
> > * Kernel testing
> > * CIP Core
> > * Software update
> > * 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,
> >
> > SZ Lin, Moxa.
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
@ 2019-03-14  9:19   ` Chris Paterson
  2019-03-14  9:23   ` Patryk Mungai Ndungu
  2019-03-15  9:24   ` Jan Kiszka
  2 siblings, 0 replies; 195+ messages in thread
From: Chris Paterson @ 2019-03-14  9:19 UTC (permalink / raw)
  To: cip-dev

Hello Daniel,

> From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-
> project.org> On Behalf Of daniel.sangorrin at toshiba.co.jp
> Sent: 14 March 2019 07:27
> 
> Hello SZ,
> 
> I can't attend today. I will write here a few updates
> 
> - I have added usbutils to CIP Core (Deby) for Patryk to use lsusb in his tests
>    - it seems to work fine now: https://lava.ciplatform.org/scheduler/job/725
>    - here is the YAML I used to test pwd, uname and lsusb. Anyone with an
> account can use it by clicking on "Resubmit" and optionally change the test:
> https://lava.ciplatform.org/scheduler/job/725/definition
Thank you for adding lsusb, and thank you for doing a trial run on the LAVA master. It's very helpful for everyone to see examples.

Kind regards, Chris

> 
> - Suzuki-san has found a couple of issues in ISAR CIP Core.
>   - when building ISAR for the beaglebone black it complains that
> "/debootstrap/debootstrap is not found" (or something like that). He will
> post a new issue on the Gitlab web page with the complete log.
>   - after building ISAR for qemu succesfully, he tried to run start-qemu.sh
> x86_64 and there was an issue with --nographics that required to add ttyS0
> (or something like that) to the qemu parameters. He will be sending a patch
> soon.
> [Note] we are planning to develop the SWUpdate demo using ISAR, any
> advice or news about how to build SWUpdate on ISAR with the right U-Boot
> environment?
> 
> - Regarding SWUpdate we hit an issue that we had not expected before.
> Suzuki-san was trying to update the standard BBB debian image (or a yocto-
> made one), but there were many warnings about orphan nodes etc. After
> some investigation the reason seems to be that the rootfs is modified during
> the first boot (or something like that). This is probably one of the biggest
> problems with updating images instead of files.
> 
> # Sorry for the "something like that"s, I have not verified by myself
> everything
> 
> #action I have to upload to the wiki the SW updates tool comparison
> document
> #action Mae please add a link to the SW updates wiki page from the
> embedded world CIP release page
> https://www.linuxfoundation.org/press-release/2019/02/civil-
> infrastructure-platform-announces-new-super-long-term-support-kernel-
> that-advances-automation-machine-learning-and-artificial-intelligence/
> 
> Thanks,
> Daniel
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-
> project.org> On Behalf Of SZ Lin (?
> > ??)
> > Sent: Thursday, March 14, 2019 10:55 AM
> > To: cip-dev at 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 IRC meeting was rescheduled to 18:00 (JST) starting from
> the first week of Nov. according to
> > F2F meeting discussion in ELCE.*
> >
> > US-West US-East? UK??? DE???? TW???? JP
> > 02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00
> >
> > Channel:
> > * irc:chat.freenode.net:6667/cip
> >
> > Agenda:
> >
> > * AI review
> > #action Iwamatsu-san will create a template page and send the link via
> mailing list afterward
> > #action Please send configuration file of kernel 4.19 to cip-dev before end
> of March.
> >
> > * Kernel maintenance updates
> > * Kernel testing
> > * CIP Core
> > * Software update
> > * 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,
> >
> > SZ Lin, Moxa.
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-14  1:55 SZ Lin (林上智)
  2019-03-14  4:38 ` Nobuhiro Iwamatsu
@ 2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
  2019-03-14  9:19   ` Chris Paterson
                     ` (2 more replies)
  1 sibling, 3 replies; 195+ messages in thread
From: daniel.sangorrin at toshiba.co.jp @ 2019-03-14  7:26 UTC (permalink / raw)
  To: cip-dev

Hello SZ,

I can't attend today. I will write here a few updates

- I have added usbutils to CIP Core (Deby) for Patryk to use lsusb in his tests
   - it seems to work fine now: https://lava.ciplatform.org/scheduler/job/725
   - here is the YAML I used to test pwd, uname and lsusb. Anyone with an account can use it by clicking on "Resubmit" and optionally change the test: https://lava.ciplatform.org/scheduler/job/725/definition

- Suzuki-san has found a couple of issues in ISAR CIP Core.
  - when building ISAR for the beaglebone black it complains that "/debootstrap/debootstrap is not found" (or something like that). He will post a new issue on the Gitlab web page with the complete log.
  - after building ISAR for qemu succesfully, he tried to run start-qemu.sh x86_64 and there was an issue with --nographics that required to add ttyS0 (or something like that) to the qemu parameters. He will be sending a patch soon.
[Note] we are planning to develop the SWUpdate demo using ISAR, any advice or news about how to build SWUpdate on ISAR with the right U-Boot environment?

- Regarding SWUpdate we hit an issue that we had not expected before. Suzuki-san was trying to update the standard BBB debian image (or a yocto-made one), but there were many warnings about orphan nodes etc. After some investigation the reason seems to be that the rootfs is modified during the first boot (or something like that). This is probably one of the biggest problems with updating images instead of files.

# Sorry for the "something like that"s, I have not verified by myself everything

#action I have to upload to the wiki the SW updates tool comparison document
#action Mae please add a link to the SW updates wiki page from the embedded world CIP release page
https://www.linuxfoundation.org/press-release/2019/02/civil-infrastructure-platform-announces-new-super-long-term-support-kernel-that-advances-automation-machine-learning-and-artificial-intelligence/

Thanks,
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, March 14, 2019 10:55 AM
> To: cip-dev at 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 IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to
> F2F meeting discussion in ELCE.*
> 
> US-West US-East? UK??? DE???? TW???? JP
> 02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> 
> * AI review
> #action Iwamatsu-san will create a template page and send the link via mailing list afterward
> #action Please send configuration file of kernel 4.19 to cip-dev before end of March.
> 
> * Kernel maintenance updates
> * Kernel testing
> * CIP Core
> * Software update
> * 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,
> 
> SZ Lin, Moxa.
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-03-14  1:55 SZ Lin (林上智)
@ 2019-03-14  4:38 ` Nobuhiro Iwamatsu
  2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
  1 sibling, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2019-03-14  4:38 UTC (permalink / raw)
  To: cip-dev

Hi, SZ
I can not join IRC meeting today by personal reason.

2019?3?14?(?) 10:55 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi all,
>
> Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
>
> *Please note that IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*
>
> US-West US-East  UK    DE     TW     JP
> 02:00    05:00   09:00   10:00   17:00   18:00
>
> Channel:
> * irc:chat.freenode.net:6667/cip
>
> Agenda:
>
> * AI review
> #action Iwamatsu-san will create a template page and send the link via mailing list afterward

I sent a mail about this.

> #action Please send configuration file of kernel 4.19 to cip-dev before end of March.
>
> * Kernel maintenance updates

I have no update.
I am working on releasing a new CIP kernel, but this is delayed.


> * Kernel testing
> * CIP Core
> * Software update
> * 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,
>
> SZ Lin, Moxa.

Best regards,
  Nobuhiro

> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-03-14  1:55 SZ Lin (林上智)
  2019-03-14  4:38 ` Nobuhiro Iwamatsu
  2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
  0 siblings, 2 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-03-14  1:55 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Iwamatsu-san will create a template page and send the link via mailing list afterward
#action Please send configuration file of kernel 4.19 to cip-dev before end of March.?

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update?
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-03-07  2:19 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-03-07  2:19 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that? IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Iwamatsu-san will introduce kernel patch review mechanism in 3/7 IRC meeting

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update?
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-02-21  5:31 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-02-21  5:31 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East  UK    DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:


* AI review
* Kernel maintenance updates
* Kernel testing
* CIP Core

* Software update
* 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,

SZ Lin, Moxa.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190221/521d457f/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-02-14  6:33 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-02-14  6:33 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East  UK    DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Kernel maintenance updates
* Kernel testing
* CIP Core

* Software update
* 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,

SZ Lin, Moxa.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190214/c3b4bf78/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-02-07  2:29 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-02-07  2:29 UTC (permalink / raw)
  To: cip-dev

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that? IRC meeting was rescheduled to 18:00 (JST) starting from the first week of Nov. according to F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Iwamatsu will release v4.4.172 cip kernel today
->Iwamatsu released v4.4.171 kernel [1]
[1] https://lists.cip-project.org/pipermail/cip-dev/2019-January/001769.html

#action Sangorrin will list of packages for cip core v2 tiny profile
-> Sangorrin has sent the list [2]
[2]https://lists.cip-project.org/pipermail/cip-dev/2019-February/001776.html

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update?
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-01-24  7:29 ` Nobuhiro Iwamatsu
@ 2019-01-24  7:56   ` SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-01-24  7:56 UTC (permalink / raw)
  To: cip-dev

Hi Iwamatsu-san,

Noted with thanks.

SZ

-----Original Message-----
From: Nobuhiro Iwamatsu [mailto:nobuhiro.iwamatsu at miraclelinux.com] 
Sent: Thursday, January 24, 2019 3:30 PM
To: SZ Lin (???) <SZ.Lin@moxa.com>
Cc: cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi, SZ.

Sorry I?m afraid I can't join this week's IRC meeting.
For Kernel maintenance updates, I don't have no update.

Best regards,
  Nobuhiro

2019?1?24?(?) 11:23 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi All,
>
>
>
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
>
>
>
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*
>
>
>
> US-West US-East  UK    DE     TW     JP
>
> 02:00    05:00   09:00   10:00   17:00   18:00
>
>
>
> Channel:
>
> * irc:chat.freenode.net:6667/cip
>
>
>
> Agenda:
>
>
>
> * Kernel maintenance updates
>
> TBD: wiki page edit
>
> * Kernel testing
>
> * Software update
>
> * CIP Core
>
> * 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,
>
>
>
> SZ Lin, Moxa.
>
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-01-24  2:22 SZ Lin (林上智)
  2019-01-24  3:00 ` daniel.sangorrin at toshiba.co.jp
@ 2019-01-24  7:29 ` Nobuhiro Iwamatsu
  2019-01-24  7:56   ` SZ Lin (林上智)
  1 sibling, 1 reply; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2019-01-24  7:29 UTC (permalink / raw)
  To: cip-dev

Hi, SZ.

Sorry I?m afraid I can't join this week's IRC meeting.
For Kernel maintenance updates, I don't have no update.

Best regards,
  Nobuhiro

2019?1?24?(?) 11:23 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi All,
>
>
>
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
>
>
>
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*
>
>
>
> US-West US-East  UK    DE     TW     JP
>
> 02:00    05:00   09:00   10:00   17:00   18:00
>
>
>
> Channel:
>
> * irc:chat.freenode.net:6667/cip
>
>
>
> Agenda:
>
>
>
> * Kernel maintenance updates
>
> TBD: wiki page edit
>
> * Kernel testing
>
> * Software update
>
> * CIP Core
>
> * 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,
>
>
>
> SZ Lin, Moxa.
>
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-01-24  5:40   ` SZ Lin (林上智)
@ 2019-01-24  5:49     ` daniel.sangorrin at toshiba.co.jp
  0 siblings, 0 replies; 195+ messages in thread
From: daniel.sangorrin at toshiba.co.jp @ 2019-01-24  5:49 UTC (permalink / raw)
  To: cip-dev

Hi SZ,
Cc: Jan, Wolfgang

Sorry I have no updates. A bit busy these days.
Just I wanted to say to Jan that the backlinks to cip-core seem to be all ours [1], so he can go ahead and modify the directory structure in gitlab.
Also, I wanted to ask Siemens to fill the cip-core survey (the software updates survey is done).

[1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core-quickstart

Thanks,
Daniel

> -----Original Message-----
> From: SZ Lin (???) <SZ.Lin@moxa.com>
> Sent: Thursday, January 24, 2019 2:40 PM
> To: sangorrin daniel(????? ???? ????????) <daniel.sangorrin@toshiba.co.jp>;
> cip-dev at lists.cip-project.org
> Subject: RE: CIP IRC weekly meeting today
> 
> Hi Daniel,
> 
> Thanks for the heads up.
> 
> It would be great if you can update the status via email before the meeting.
> 
> SZ
> 
> -----Original Message-----
> From: daniel.sangorrin at toshiba.co.jp [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Thursday, January 24, 2019 11:00 AM
> To: SZ Lin (???) <SZ.Lin@moxa.com>; cip-dev at lists.cip-project.org
> Subject: RE: CIP IRC weekly meeting today
> 
> Hi Sz,
> I'm afraid I won't be able to attend.
> Regards
> Daniel
> 
> > -----Original Message-----
> > From: cip-dev-bounces at lists.cip-project.org
> > <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (?
> > ??)
> > Sent: Thursday, January 24, 2019 11:23 AM
> > To: cip-dev at lists.cip-project.org
> > Subject: [cip-dev] CIP IRC weekly meeting today
> >
> > Hi All,
> >
> >
> >
> > Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
> >
> >
> >
> > *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting
> > from first week of Nov. according F2F meeting discussion in ELCE.*
> >
> >
> >
> > US-West US-East  UK    DE     TW     JP
> >
> > 02:00    05:00   09:00   10:00   17:00   18:00
> >
> >
> >
> > Channel:
> >
> > * irc:chat.freenode.net:6667/cip
> >
> >
> >
> > Agenda:
> >
> >
> >
> > * Kernel maintenance updates
> >
> > TBD: wiki page edit
> >
> > * Kernel testing
> >
> > * Software update
> >
> > * CIP Core
> >
> > * 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,
> >
> >
> >
> > SZ Lin, Moxa.
> >
> >

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-01-24  3:00 ` daniel.sangorrin at toshiba.co.jp
@ 2019-01-24  5:40   ` SZ Lin (林上智)
  2019-01-24  5:49     ` daniel.sangorrin at toshiba.co.jp
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-01-24  5:40 UTC (permalink / raw)
  To: cip-dev

Hi Daniel,

Thanks for the heads up.

It would be great if you can update the status via email before the meeting.

SZ

-----Original Message-----
From: daniel.sangorrin@toshiba.co.jp [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Thursday, January 24, 2019 11:00 AM
To: SZ Lin (???) <SZ.Lin@moxa.com>; cip-dev at lists.cip-project.org
Subject: RE: CIP IRC weekly meeting today

Hi Sz,
I'm afraid I won't be able to attend.
Regards
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org 
> <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, January 24, 2019 11:23 AM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] CIP IRC weekly meeting today
> 
> Hi All,
> 
> 
> 
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 
> 
> 
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting 
> from first week of Nov. according F2F meeting discussion in ELCE.*
> 
> 
> 
> US-West US-East  UK    DE     TW     JP
> 
> 02:00    05:00   09:00   10:00   17:00   18:00
> 
> 
> 
> Channel:
> 
> * irc:chat.freenode.net:6667/cip
> 
> 
> 
> Agenda:
> 
> 
> 
> * Kernel maintenance updates
> 
> TBD: wiki page edit
> 
> * Kernel testing
> 
> * Software update
> 
> * CIP Core
> 
> * 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,
> 
> 
> 
> SZ Lin, Moxa.
> 
> 

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2019-01-24  2:22 SZ Lin (林上智)
@ 2019-01-24  3:00 ` daniel.sangorrin at toshiba.co.jp
  2019-01-24  5:40   ` SZ Lin (林上智)
  2019-01-24  7:29 ` Nobuhiro Iwamatsu
  1 sibling, 1 reply; 195+ messages in thread
From: daniel.sangorrin at toshiba.co.jp @ 2019-01-24  3:00 UTC (permalink / raw)
  To: cip-dev

Hi Sz, 
I'm afraid I won't be able to attend.
Regards
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (?
> ??)
> Sent: Thursday, January 24, 2019 11:23 AM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] CIP IRC weekly meeting today
> 
> Hi All,
> 
> 
> 
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
> 
> 
> 
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F
> meeting discussion in ELCE.*
> 
> 
> 
> US-West US-East  UK    DE     TW     JP
> 
> 02:00    05:00   09:00   10:00   17:00   18:00
> 
> 
> 
> Channel:
> 
> * irc:chat.freenode.net:6667/cip
> 
> 
> 
> Agenda:
> 
> 
> 
> * Kernel maintenance updates
> 
> TBD: wiki page edit
> 
> * Kernel testing
> 
> * Software update
> 
> * CIP Core
> 
> * 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,
> 
> 
> 
> SZ Lin, Moxa.
> 
> 

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-01-24  2:22 SZ Lin (林上智)
  2019-01-24  3:00 ` daniel.sangorrin at toshiba.co.jp
  2019-01-24  7:29 ` Nobuhiro Iwamatsu
  0 siblings, 2 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-01-24  2:22 UTC (permalink / raw)
  To: cip-dev

Hi All,



Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*



US-West US-East  UK    DE     TW     JP

02:00    05:00   09:00   10:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Kernel maintenance updates

TBD: wiki page edit

* Kernel testing

* Software update

* CIP Core

* 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,



SZ Lin, Moxa.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190124/c534bbaf/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2019-01-17  2:30 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2019-01-17  2:30 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that? IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* AI review
#action Daniel will start to work on v4.4.166-cip29-rt21 this friday? 
* Kernel maintenance updates
* Kernel testing
* Software update 
* CIP Core
* 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..

I won't be able to attend this meeting, Gavin will chair today's meeting.

Best regards,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-12-27  2:10 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-12-27  2:10 UTC (permalink / raw)
  To: cip-dev

Hi All,



Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*



US-West US-East  UK    DE     TW     JP

02:00    05:00   09:00   10:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* Kernel maintenance updates

* Kernel testing

* CIP Core

* Software update

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181227/1689c9b4/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-12-20  2:05 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-12-20  2:05 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that? IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*

US-West US-East? UK??? DE???? TW???? JP
02:00??? 05:00?? 09:00?? 10:00?? 17:00?? 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Kernel maintenance updates
* Kernel testing
* CIP Core
* Software update 
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-12-13  2:55 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-12-13  2:55 UTC (permalink / raw)
  To: cip-dev

Hi All,



Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*



US-West US-East  UK    DE     TW     JP

02:00    05:00   09:00   10:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* AI review

#action Confirm the specified release date for 4.19-CIP release. (During or after the Embedded World? 28th Feb.)

* Kernel maintenance updates

* Kernel testing

* Software update

* CIP Core

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181213/acf1f6f9/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2018-12-06  6:10   ` SZ Lin (林上智)
@ 2018-12-10 12:30     ` Nobuhiro Iwamatsu
  0 siblings, 0 replies; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2018-12-10 12:30 UTC (permalink / raw)
  To: cip-dev

Hi, SZ.

2018?12?6?(?) 15:10 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi Nobuhiro,
>
> Thanks for the heads up.
>
> Could you update the status of below action item?
>
> #action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week
>

I sent mail about this  a few hours ago. Sorry for the delay.

Best regards,
  Nobuhiro

> SZ
>
> -----Original Message-----
> From: Nobuhiro Iwamatsu [mailto:nobuhiro.iwamatsu at miraclelinux.com]
> Sent: Thursday, December 06, 2018 1:42 PM
> To: SZ Lin (???) <SZ.Lin@moxa.com>
> Cc: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] CIP IRC weekly meeting today
>
> Hi,  SZ.
>
> I have other schedule today so I can not participate in the meeting.
> Sorry.
>
> Best regards,
>   Nobuhiro
> 2018?12?6?(?) 12:23 SZ Lin (???) <SZ.Lin@moxa.com>:
> >
> > Hi All,
> >
> >
> >
> > Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
> >
> >
> >
> > *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*
> >
> >
> >
> > US-West US-East  UK    DE     TW     JP
> >
> > 02:00    05:00   09:00   10:00   17:00   18:00
> >
> >
> >
> > Channel:
> >
> > * irc:chat.freenode.net:6667/cip
> >
> >
> >
> > Agenda:
> >
> >
> >
> > * AI review
> >
> > #action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week
> >
> > #action CIP members fill out the SW Updates requirements survey before 12/10.
> >
> > * Kernel maintenance updates
> >
> > * Kernel testing
> >
> > * Software update
> >
> > * CIP Core
> >
> > * 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,
> >
> >
> >
> > SZ Lin, Moxa.
> >
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2018-12-06  5:41 ` Nobuhiro Iwamatsu
@ 2018-12-06  6:10   ` SZ Lin (林上智)
  2018-12-10 12:30     ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-12-06  6:10 UTC (permalink / raw)
  To: cip-dev

Hi Nobuhiro,

Thanks for the heads up.

Could you update the status of below action item?

#action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week

SZ

-----Original Message-----
From: Nobuhiro Iwamatsu [mailto:nobuhiro.iwamatsu at miraclelinux.com] 
Sent: Thursday, December 06, 2018 1:42 PM
To: SZ Lin (???) <SZ.Lin@moxa.com>
Cc: cip-dev at lists.cip-project.org
Subject: Re: [cip-dev] CIP IRC weekly meeting today

Hi,  SZ.

I have other schedule today so I can not participate in the meeting.
Sorry.

Best regards,
  Nobuhiro
2018?12?6?(?) 12:23 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi All,
>
>
>
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
>
>
>
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*
>
>
>
> US-West US-East  UK    DE     TW     JP
>
> 02:00    05:00   09:00   10:00   17:00   18:00
>
>
>
> Channel:
>
> * irc:chat.freenode.net:6667/cip
>
>
>
> Agenda:
>
>
>
> * AI review
>
> #action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week
>
> #action CIP members fill out the SW Updates requirements survey before 12/10.
>
> * Kernel maintenance updates
>
> * Kernel testing
>
> * Software update
>
> * CIP Core
>
> * 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,
>
>
>
> SZ Lin, Moxa.
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2018-12-06  3:22 SZ Lin (林上智)
@ 2018-12-06  5:41 ` Nobuhiro Iwamatsu
  2018-12-06  6:10   ` SZ Lin (林上智)
  0 siblings, 1 reply; 195+ messages in thread
From: Nobuhiro Iwamatsu @ 2018-12-06  5:41 UTC (permalink / raw)
  To: cip-dev

Hi,  SZ.

I have other schedule today so I can not participate in the meeting.
Sorry.

Best regards,
  Nobuhiro
2018?12?6?(?) 12:23 SZ Lin (???) <SZ.Lin@moxa.com>:
>
> Hi All,
>
>
>
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.
>
>
>
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*
>
>
>
> US-West US-East  UK    DE     TW     JP
>
> 02:00    05:00   09:00   10:00   17:00   18:00
>
>
>
> Channel:
>
> * irc:chat.freenode.net:6667/cip
>
>
>
> Agenda:
>
>
>
> * AI review
>
> #action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week
>
> #action CIP members fill out the SW Updates requirements survey before 12/10.
>
> * Kernel maintenance updates
>
> * Kernel testing
>
> * Software update
>
> * CIP Core
>
> * 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,
>
>
>
> SZ Lin, Moxa.
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-12-06  3:22 SZ Lin (林上智)
  2018-12-06  5:41 ` Nobuhiro Iwamatsu
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-12-06  3:22 UTC (permalink / raw)
  To: cip-dev

Hi All,



Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.



*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*



US-West US-East  UK    DE     TW     JP

02:00    05:00   09:00   10:00   17:00   18:00



Channel:

* irc:chat.freenode.net:6667/cip



Agenda:



* AI review

#action Iwamatsu will send the merging schedule of CIP kernel to ML (cip-dev) this week

#action CIP members fill out the SW Updates requirements survey before 12/10.

* Kernel maintenance updates

* Kernel testing

* Software update

* CIP Core

* 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,



SZ Lin, Moxa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181206/d8d65e25/attachment.html>

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-11-29  1:27 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-11-29  1:27 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*

US-West US-East  UK    DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:

* Kernel maintenance updates
* Kernel testing
* Software update 
* CIP Core
* 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,

SZ Lin, Moxa.

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
  2018-11-22  4:41 SZ Lin (林上智)
@ 2018-11-22  6:29 ` Daniel Sangorrin
  0 siblings, 0 replies; 195+ messages in thread
From: Daniel Sangorrin @ 2018-11-22  6:29 UTC (permalink / raw)
  To: cip-dev

Hi SZ,

I won't be able to attend the meeting today.
I just sent a few e-mails for the CIP Software update workgroup and the CIP Core workgroup on the members list.
I want to continue that conversation on the members list for now, before we start development.

Thanks,
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> <cip-dev-bounces@lists.cip-project.org> On Behalf Of SZ Lin (???)
> Sent: Thursday, November 22, 2018 1:42 PM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] CIP IRC weekly meeting today
> 
> Hi All,
> 
> Kindly be reminded to attend weekly meeting through IRC to discuss technical topics
> with CIP kernel today.
> 
> *Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first
> week of Nov. according F2F meeting discussion in ELCE.*
> 
> US-West US-East  UK    DE     TW     JP
> 02:00    05:00   09:00   10:00   17:00   18:00
> 
> Channel:
> * irc:chat.freenode.net:6667/cip
> 
> Agenda:
> * AI review
> - #action Make sure armhf is available in Debian 10 (or not)
> - #action Daniel will send cip-core questions to cip-members ML
> 
> * Kernel maintenance updates
> * Kernel testing
> * Software update
> * CIP Core
> * 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,
> 
> SZ Lin
> 
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-11-22  4:41 SZ Lin (林上智)
  2018-11-22  6:29 ` Daniel Sangorrin
  0 siblings, 1 reply; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-11-22  4:41 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*

US-West US-East  UK    DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:
* AI review
- #action Make sure armhf is available in Debian 10 (or not)
- #action Daniel will send cip-core questions to cip-members ML

* Kernel maintenance updates
* Kernel testing
* Software update 
* CIP Core
* 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,

SZ Lin

^ permalink raw reply	[flat|nested] 195+ messages in thread

* [cip-dev] CIP IRC weekly meeting today
@ 2018-11-15  3:32 SZ Lin (林上智)
  0 siblings, 0 replies; 195+ messages in thread
From: SZ Lin (林上智) @ 2018-11-15  3:32 UTC (permalink / raw)
  To: cip-dev

Hi All,

Kindly be reminded to attend weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that  IRC meeting was rescheduled to 18:00 (JST) starting from first week of Nov. according F2F meeting discussion in ELCE.*

US-West US-East  UK    DE     TW     JP
02:00    05:00   09:00   10:00   17:00   18:00

Channel:
* irc:chat.freenode.net:6667/cip

Agenda:
* Kernel maintenance updates
* Kernel testing
* Software update 
* CIP Core
* 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,

SZ Lin

^ permalink raw reply	[flat|nested] 195+ messages in thread

end of thread, back to index

Thread overview: 195+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-08  0:56 [cip-dev] CIP IRC weekly meeting today masashi.kudo
2020-10-08  2:40 ` Kento Yoshida
2020-10-08  5:46 ` Nobuhiro Iwamatsu
2020-10-08  8:19 ` Chen-Yu Tsai (Moxa)
  -- strict thread matches above, loose matches on Subject: below --
2020-10-21 23:50 masashi.kudo
2020-10-15  0:17 masashi.kudo
2020-10-01  0:27 masashi.kudo
2020-10-01  4:37 ` Chen-Yu Tsai (Moxa)
2020-10-01  5:37 ` Chris Paterson
2020-10-01  8:11 ` Pavel Machek
2020-09-24  0:58 masashi.kudo
2020-09-24  2:42 ` Akihiro Suzuki
2020-09-17  1:20 masashi.kudo
2020-09-17  6:58 ` Akihiro Suzuki
2020-09-10  0:23 masashi.kudo
2020-09-10  7:08 ` Nobuhiro Iwamatsu
2020-09-03  0:09 masashi.kudo
2020-08-27  0:58 masashi.kudo
2020-08-27  5:04 ` Akihiro Suzuki
2020-08-20  0:21 masashi.kudo
2020-08-05 23:51 masashi.kudo
2020-08-06  2:42 ` Akihiro Suzuki
2020-07-30  1:56 masashi.kudo
2020-07-30  8:39 ` Akihiro Suzuki
2020-07-23  2:58 masashi.kudo
2020-07-23  7:32 ` Pavel Machek
2020-07-24  8:27 ` Chris Paterson
2020-07-16  1:29 masashi.kudo
2020-07-16  6:11 ` Chen-Yu Tsai (Moxa)
2020-07-16  8:27 ` Nobuhiro Iwamatsu
2020-07-08 22:42 masashi.kudo
2020-07-09  7:06 ` Pavel Machek
2020-07-01 22:53 masashi.kudo
2020-07-02  8:43 ` Chris Paterson
2020-07-02  8:49   ` masashi.kudo
2020-06-25  1:53 masashi.kudo
2020-06-25  7:00 ` Pavel Machek
2020-06-25  7:03   ` masashi.kudo
2020-06-18  0:20 masashi.kudo
2020-06-18  2:12 ` masashi.kudo
2020-06-18  7:19 ` Nobuhiro Iwamatsu
2020-06-18  7:27   ` masashi.kudo
2020-06-10 23:55 masashi.kudo
2020-06-11 11:23 ` Pavel Machek
2020-06-11 11:47   ` masashi.kudo
2020-06-04  2:38 masashi.kudo
2020-06-04  6:58 ` Akihiro Suzuki
2020-06-04  7:12   ` masashi.kudo
2020-05-28  1:26 masashi.kudo
2020-05-21  0:36 masashi.kudo
2020-05-21  6:08 ` Nobuhiro Iwamatsu
2020-05-21  7:12   ` masashi.kudo
2020-05-13 23:27 masashi.kudo
2020-05-06 22:28 masashi.kudo
2020-04-23  0:06 masashi.kudo
2020-04-23  8:41 ` Akihiro Suzuki
2020-04-23  8:43   ` masashi.kudo
2020-04-16  2:02 masashi.kudo
2020-04-16  7:21 ` punit1.agrawal
2020-04-16  7:28   ` masashi.kudo
2020-04-16  8:15 ` Chris Paterson
2020-04-16  8:18   ` masashi.kudo
2020-04-08 23:24 masashi.kudo
2020-04-02  0:30 masashi.kudo
2020-04-02  8:19 ` nobuhiro1.iwamatsu
2020-04-02  8:22   ` masashi.kudo
2020-03-25 22:52 masashi.kudo
2020-03-18 22:35 masashi.kudo
2020-03-19  8:17 ` nobuhiro1.iwamatsu
2020-03-19  8:20   ` masashi.kudo
2020-03-11 23:42 masashi.kudo
2020-03-05  0:28 masashi.kudo
2020-02-19 23:09 masashi.kudo
2020-02-13  1:31 masashi.kudo at cybertrust.co.jp
2020-02-05 22:58 masashi.kudo at cybertrust.co.jp
2020-02-06  7:25 ` nobuhiro1.iwamatsu at toshiba.co.jp
2020-02-06  8:04   ` masashi.kudo at cybertrust.co.jp
2020-01-29 22:54 masashi.kudo at cybertrust.co.jp
2020-01-30  7:35 ` Chris Paterson
2020-01-30  8:05   ` masashi.kudo at cybertrust.co.jp
2020-01-30 13:29 ` masashi.kudo at cybertrust.co.jp
2020-01-22 22:55 masashi.kudo at cybertrust.co.jp
2020-01-23  8:33 ` Chen-Yu Tsai
2020-01-23  8:35   ` masashi.kudo at cybertrust.co.jp
2020-01-15 23:16 masashi.kudo at cybertrust.co.jp
2020-01-16  8:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
2020-01-09  0:56 masashi.kudo at cybertrust.co.jp
2019-12-25 22:52 masashi.kudo at cybertrust.co.jp
2019-12-18 23:39 masashi.kudo at cybertrust.co.jp
2019-12-12  0:59 masashi.kudo at cybertrust.co.jp
2019-12-12  7:04 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-12-12  9:50 ` masashi.kudo at cybertrust.co.jp
2019-12-12 12:56   ` masashi.kudo at cybertrust.co.jp
2019-12-05  0:28 masashi.kudo at cybertrust.co.jp
2019-11-28  1:51 SZ Lin (林上智)
2019-11-21  0:30 SZ Lin (林上智)
2019-11-21  7:38 ` Nobuhiro Iwamatsu
2019-11-21  8:53 ` Chris Paterson
2019-11-14  1:41 SZ Lin (林上智)
2019-11-07  1:56 SZ Lin (林上智)
2019-11-07  7:15 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-11-07  9:17   ` SZ Lin (林上智)
2019-10-24  1:55 SZ Lin (林上智)
2019-10-24  5:50 ` masashi.kudo at cybertrust.co.jp
2019-10-24  5:53   ` SZ Lin (林上智)
2019-10-24  6:01     ` masashi.kudo at cybertrust.co.jp
2019-10-17  2:05 SZ Lin (林上智)
2019-10-10  2:32 SZ Lin (林上智)
2019-10-03  1:56 SZ Lin (林上智)
2019-09-26  2:46 SZ Lin (林上智)
     [not found] ` <CAFa_k0gBzv-2bOF_pGbpvZQyQ1ocEu-bsBNT_JsWi12cxrK-Pg@mail.gmail.com>
2019-09-26  3:01   ` masashi.kudo at cybertrust.co.jp
2019-09-28  4:30     ` masashi.kudo at cybertrust.co.jp
2019-09-30  7:19       ` Chris Paterson
2019-10-01  2:47     ` masashi.kudo at cybertrust.co.jp
2019-09-19  1:27 SZ Lin (林上智)
2019-09-19 11:08 ` Pavel Machek
2019-09-12  1:37 SZ Lin (林上智)
2019-09-12 22:46 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-09-05  1:34 SZ Lin (林上智)
2019-08-29  1:31 SZ Lin (林上智)
2019-08-29  2:51 ` masashi.kudo at cybertrust.co.jp
2019-08-29  4:05   ` SZ Lin (林上智)
2019-08-29  7:13     ` masashi.kudo at cybertrust.co.jp
2019-08-22  1:31 SZ Lin (林上智)
2019-08-22 20:35 ` Pavel Machek
2019-08-15  1:04 SZ Lin (林上智)
2019-08-08  1:55 SZ Lin (林上智)
2019-08-01  1:03 SZ Lin (林上智)
2019-08-01  8:05 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-25  1:06 SZ Lin (林上智)
2019-07-11  2:25 SZ Lin (林上智)
2019-07-04  0:59 SZ Lin (林上智)
2019-07-04  6:38 ` akihiro27.suzuki at toshiba.co.jp
2019-06-27  0:29 SZ Lin (林上智)
2019-06-27  5:53 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-06-20  1:11 SZ Lin (林上智)
2019-06-12 23:26 SZ Lin (林上智)
2019-06-13  6:56 ` Chris Paterson
2019-06-06  1:28 SZ Lin (林上智)
2019-06-06  2:01 ` kazuhiro3.hayashi at toshiba.co.jp
2019-05-30  1:18 SZ Lin (林上智)
2019-05-23  1:58 SZ Lin (林上智)
2019-05-16  3:55 SZ Lin (林上智)
2019-05-09  1:45 SZ Lin (林上智)
2019-04-25  2:34 SZ Lin (林上智)
2019-04-18  1:33 SZ Lin (林上智)
2019-04-11  2:28 SZ Lin (林上智)
2019-04-04  2:52 SZ Lin (林上智)
2019-03-28  4:08 SZ Lin (林上智)
2019-03-21  0:48 SZ Lin (林上智)
2019-03-14  1:55 SZ Lin (林上智)
2019-03-14  4:38 ` Nobuhiro Iwamatsu
2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
2019-03-14  9:19   ` Chris Paterson
2019-03-14  9:23   ` Patryk Mungai Ndungu
2019-03-15  9:24   ` Jan Kiszka
2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
2019-03-15 10:50       ` Jan Kiszka
2019-03-18  1:42         ` akihiro27.suzuki at toshiba.co.jp
2019-03-18  2:53         ` akihiro27.suzuki at toshiba.co.jp
2019-03-18  8:42     ` Christian Storm
2019-03-18  9:14       ` akihiro27.suzuki at toshiba.co.jp
2019-03-18 10:27         ` Christian Storm
2019-03-22  5:01           ` akihiro27.suzuki at toshiba.co.jp
2019-03-22 12:37             ` Christian Storm
2019-03-27  8:25               ` akihiro27.suzuki at toshiba.co.jp
2019-03-29 13:21                 ` Christian Storm
2019-04-01  2:48                   ` akihiro27.suzuki at toshiba.co.jp
2019-04-01  6:48                     ` Christian Storm
2019-04-02  3:50                       ` akihiro27.suzuki at toshiba.co.jp
2019-04-02  6:45                         ` Christian Storm
2019-04-02  8:14                           ` akihiro27.suzuki at toshiba.co.jp
2019-04-26 10:34                           ` akihiro27.suzuki at toshiba.co.jp
2019-03-07  2:19 SZ Lin (林上智)
2019-02-21  5:31 SZ Lin (林上智)
2019-02-14  6:33 SZ Lin (林上智)
2019-02-07  2:29 SZ Lin (林上智)
2019-01-24  2:22 SZ Lin (林上智)
2019-01-24  3:00 ` daniel.sangorrin at toshiba.co.jp
2019-01-24  5:40   ` SZ Lin (林上智)
2019-01-24  5:49     ` daniel.sangorrin at toshiba.co.jp
2019-01-24  7:29 ` Nobuhiro Iwamatsu
2019-01-24  7:56   ` SZ Lin (林上智)
2019-01-17  2:30 SZ Lin (林上智)
2018-12-27  2:10 SZ Lin (林上智)
2018-12-20  2:05 SZ Lin (林上智)
2018-12-13  2:55 SZ Lin (林上智)
2018-12-06  3:22 SZ Lin (林上智)
2018-12-06  5:41 ` Nobuhiro Iwamatsu
2018-12-06  6:10   ` SZ Lin (林上智)
2018-12-10 12:30     ` Nobuhiro Iwamatsu
2018-11-29  1:27 SZ Lin (林上智)
2018-11-22  4:41 SZ Lin (林上智)
2018-11-22  6:29 ` Daniel Sangorrin
2018-11-15  3:32 SZ Lin (林上智)

CIP-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/cip-dev/0 cip-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 cip-dev cip-dev/ https://lore.kernel.org/cip-dev \
		cip-dev@lists.cip-project.org
	public-inbox-index cip-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.cip-project.lists.cip-dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git