Hi!

6.1.16-rc1 review was announced, and I guess this would be great time to
announce that we are now testing it.

I see tree at:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commits/ci/patersonc/linux-6.1.y

...but that one is does not contain recent commits from 6.1.16-rc1.

I see it updates from linux-cip. I believe it should update from
stable@....

Ideally, I'd like to see same setup we have at

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y

... (And prefferably do it at the same address).

Thanks and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Hello Pavel,

From: Pavel Machek <pavel@...>
Sent: 07 March 2023 21:23

Hi!

6.1.16-rc1 review was announced, and I guess this would be great time to
announce that we are now testing it.

I see tree at:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-
/commits/ci/patersonc/linux-6.1.y

...but that one is does not contain recent commits from 6.1.16-rc1.

Nope; it was just a dev branch using whatever version of 6.1 was around a week or so ago.

I see it updates from linux-cip. I believe it should update from
stable@....

Ideally, I'd like to see same setup we have at

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-
5.10.y

This was the original plan. I was just using linux-cip for testing.

I've now added everything needed to run all the testing in the linux-stable-rc-ci repository.
You can see all the latest pipelines for each branch here: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines?scope=branches&page=1

As part of this work I've also improved the way the version gets logged/added to a commit.
So now it's easier to work out which version of stable-rc is being built.
e.g.
old approach: Upstream SHA: a1a87af47a80
new approach: Linux 5.10.173-rc1 (a1a87af47a80)

At the moment it's using dev branches for the linux-cip-ci, linux-cip-pipelines and cip-kernel-config repos.
I'll create MRs for these tomorrow, as I'd like some reviews on these to check that the correct compiler is being used, and the correct kernel configs are being used etc.

Kind regards, Chris

... (And prefferably do it at the same address).

Thanks and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Hello kernel team,

From: cip-dev@... <cip-dev@...> On
Behalf Of Chris Paterson via lists.cip-project.org
Sent: 09 March 2023 00:30

Hello Pavel,

From: Pavel Machek <pavel@...>
Sent: 07 March 2023 21:23

Hi!

6.1.16-rc1 review was announced, and I guess this would be great time to
announce that we are now testing it.

I see tree at:

https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab
.com%2Fcip-project%2Fcip-kernel%2Flinux-cip%2F-
&data=05%7C01%7Cchris.paterson2%40renesas.com%7C46e6166cbae948ba
bfe208db203569ff%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C63
8139186004876256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
&sdata=pteLIHqxGffWyIjkCrBdhPChoMNqd8a2Pw0RrOFZpsY%3D&reserved
=0

/commits/ci/patersonc/linux-6.1.y

...but that one is does not contain recent commits from 6.1.16-rc1.

Nope; it was just a dev branch using whatever version of 6.1 was around a
week or so ago.

I see it updates from linux-cip. I believe it should update from
stable@....

Ideally, I'd like to see same setup we have at

https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab
.com%2Fcip-project%2Fcip-testing%2Flinux-stable-rc-ci%2F-
%2Ftree%2Flinux-
&data=05%7C01%7Cchris.paterson2%40renesas.com%7C46e6166cbae948ba
bfe208db203569ff%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C63
8139186004876256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
&sdata=Xm%2FLmFoOAcMGQQia7kDJSE4WhTgB4BtD0%2BDQyEnuL24%3D&
reserved=0

5.10.y

This was the original plan. I was just using linux-cip for testing.

I've now added everything needed to run all the testing in the linux-stable-
rc-ci repository.
You can see all the latest pipelines for each branch here:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab
.com%2Fcip-project%2Fcip-testing%2Flinux-stable-rc-ci%2F-
%2Fpipelines%3Fscope%3Dbranches%26page%3D1&data=05%7C01%7Cchris.
paterson2%40renesas.com%7C46e6166cbae948babfe208db203569ff%7C53d
82571da1947e49cb4625a166a4a2a%7C0%7C0%7C638139186004876256%7CUn
known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6
Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bHf0G5VFdL50j3G
uxkyE7YJp8STsFjmtQ8pV98%2BeUdE%3D&reserved=0

As part of this work I've also improved the way the version gets
logged/added to a commit.
So now it's easier to work out which version of stable-rc is being built.
e.g.
old approach: Upstream SHA: a1a87af47a80
new approach: Linux 5.10.173-rc1 (a1a87af47a80)

At the moment it's using dev branches for the linux-cip-ci, linux-cip-pipelines
and cip-kernel-config repos.
I'll create MRs for these tomorrow, as I'd like some reviews on these to check
that the correct compiler is being used, and the correct kernel configs are
being used etc.

These MRs are now up.
I'd appreciate it if the below MRs can be reviewed before they are merged:
https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/merge_requests/74
https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/merge_requests/36

Thanks in advance!

Kind regards, Chris

Kind regards, Chris

... (And prefferably do it at the same address).

Thanks and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany