6.1 LTS

6.1 LTS

[Jan Kiszka]

Hi all,

in case you didn't see this yet (thanks to Florian for pointing it out):
https://lore.kernel.org/all/Y53BputYK+3djDME@kroah.com/

How could we contribute to this as CIP?

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

Re: [cip-dev] 6.1 LTS

[Pavel Machek]

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

Hi!

> in case you didn't see this yet (thanks to Florian for pointing it out):
> https://lore.kernel.org/all/Y53BputYK+3djDME@kroah.com/
> 
> How could we contribute to this as CIP?

Well, I believe we should start testing 6.1.X. 

Greg does not (and can not) know how well 6.1.X works, and it is hard
for him to call if it LTS if he's not confident with it, and that's a
place where we can help.

If we wanted to push it a bit more, at some point we may want to write
"hey this seems to work okay for our uses, and we'd like to see it as
LTS" or something like that.

On a related note, 4.9.X was discontinued; I believe we should create
configs for 4.14 and start testing that, to help with 4.4-st
maintainance.

Best regards,
								Pavel

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

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

RE: [cip-dev] 6.1 LTS

[Chris Paterson]

Hello,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Pavel Machek via lists.cip-project.org
> Sent: 15 January 2023 16:52
> 
> Hi!
> 
> > in case you didn't see this yet (thanks to Florian for pointing it out):
> >
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.k
> ernel.org%2Fall%2FY53BputYK%2B3djDME%40kroah.com%2F&data=05%7C0
> 1%7Cchris.paterson2%40renesas.com%7C3107d6089d4c46d7ad4408daf718e5
> bb%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C638093983549460
> 193%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu
> MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Mf2BG
> 64zLwKGm6Etz%2FdQGZjcrZEDOCVtB8brOGZ5h5U%3D&reserved=0
> >
> > How could we contribute to this as CIP?
> 
> Well, I believe we should start testing 6.1.X.

Agreed.

> 
> Greg does not (and can not) know how well 6.1.X works, and it is hard
> for him to call if it LTS if he's not confident with it, and that's a
> place where we can help.
> 
> If we wanted to push it a bit more, at some point we may want to write
> "hey this seems to work okay for our uses, and we'd like to see it as
> LTS" or something like that.
> 
> On a related note, 4.9.X was discontinued; I believe we should create
> configs for 4.14 and start testing that, to help with 4.4-st
> maintainance.

Is there a reason not to test the release candidates for all stable kernel versions?
(Currently we only test LTS)

Our CI will be fine with the extra workload.
It would just be a case of someone checking the results and feeding it back to the stable mailing list.

Chris

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

Re: RE: [cip-dev] 6.1 LTS

[Jan Kiszka]

On 16.01.23 11:46, Chris Paterson wrote:
> Hello,
> 
>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
>> Behalf Of Pavel Machek via lists.cip-project.org
>> Sent: 15 January 2023 16:52
>>
>> Hi!
>>
>>> in case you didn't see this yet (thanks to Florian for pointing it out):
>>>
>> https://lore.k
>> ernel.org%2Fall%2FY53BputYK%2B3djDME%40kroah.com%2F&data=05%7C0
>> 1%7Cchris.paterson2%40renesas.com%7C3107d6089d4c46d7ad4408daf718e5
>> bb%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C638093983549460
>> 193%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu
>> MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Mf2BG
>> 64zLwKGm6Etz%2FdQGZjcrZEDOCVtB8brOGZ5h5U%3D&reserved=0
>>>
>>> How could we contribute to this as CIP?
>>
>> Well, I believe we should start testing 6.1.X.
> 
> Agreed.
> 
>>
>> Greg does not (and can not) know how well 6.1.X works, and it is hard
>> for him to call if it LTS if he's not confident with it, and that's a
>> place where we can help.
>>
>> If we wanted to push it a bit more, at some point we may want to write
>> "hey this seems to work okay for our uses, and we'd like to see it as
>> LTS" or something like that.
>>
>> On a related note, 4.9.X was discontinued; I believe we should create
>> configs for 4.14 and start testing that, to help with 4.4-st
>> maintainance.
> 
> Is there a reason not to test the release candidates for all stable kernel versions?
> (Currently we only test LTS)
> 
> Our CI will be fine with the extra workload.
> It would just be a case of someone checking the results and feeding it back to the stable mailing list.
> 

Would we add value this way over existing kernel-ci runs - or don't they
exist?

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

RE: RE: [cip-dev] 6.1 LTS

[Chris Paterson]

> From: Jan Kiszka <jan.kiszka@siemens.com>
> Sent: 16 January 2023 12:23
> 
> On 16.01.23 11:46, Chris Paterson wrote:
> > Hello,
> >

[...]

> >> On a related note, 4.9.X was discontinued; I believe we should create
> >> configs for 4.14 and start testing that, to help with 4.4-st
> >> maintainance.
> >
> > Is there a reason not to test the release candidates for all stable kernel
> versions?
> > (Currently we only test LTS)
> >
> > Our CI will be fine with the extra workload.
> > It would just be a case of someone checking the results and feeding it back
> to the stable mailing list.
> >
> 
> Would we add value this way over existing kernel-ci runs - or don't they
> exist?

KernelCI test all stable versions I believe.

We have slightly different build/test coverage then KernelCI, so technically if we build/test as well, overall coverage would be increased.
e.g. we use the CIP kernel configurations, different compiler versions etc.

Chris

> 
> Jan
> 
> --
> Siemens AG, Technology
> Competence Center Embedded Linux