public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: <nobuhiro1.iwamatsu@toshiba.co.jp>,
	<cip-dev@lists.cip-project.org>, "Pavel Machek" <pavel@denx.de>
Subject: Re: [cip-dev] 4.4.302 is going to be last 4.4 release
Date: Sun, 6 Feb 2022 19:47:42 +0100	[thread overview]
Message-ID: <1ac8ef07-4bba-71ef-83da-524c1a717be0@siemens.com> (raw)
In-Reply-To: <TYAPR01MB625279122E073EFF486368C392289@TYAPR01MB6252.jpnprd01.prod.outlook.com>

On 03.02.22 08:13, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> Hi Pavel,
>> -----Original Message-----
>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
>> Behalf Of Pavel Machek
>> Sent: Wednesday, February 2, 2022 6:33 AM
>> To: jan.kiszka@siemens.com; cip-dev@lists.cip-project.org
>> Subject: [cip-dev] 4.4.302 is going to be last 4.4 release
>>
>> Hi!
>>
>> Greg says:
>>
>> # Message-Id: <20220201180822.148370751@linuxfoundation.org>
>> # Subject: [PATCH 4.4 00/25] 4.4.302-rc1 review # ...
>> # NOTE!  This is the proposed LAST 4.4.y kernel release to happen under # the
>> rules of the normal stable kernel releases.  After this one, it will # be marked
>> End-Of-Life as it has been 6 years and you really should know # better by now
>> and have moved to a newer kernel tree.  After this one, no # more security fixes
>> will be backported and you will end up with an # insecure system over time.
>> # ...
>> # Responses should be made by Thu, 03 Feb 2022 18:08:10 +0000.
>> # Anything received after that time might be too late.
>>
>> (He sometimes releases kernels before the deadline).
>>
>> We may want to make any announcements now or just after 4.4.302 is
>> released... so I guess we should start working on suitable wording.
>>
>> Something like:
>>
>> CIP project is committed to maintain 4.4.x kernel till January of 2027 [1]. We are
>> maintaining -cip branch [2], that is stable kernel with about
>> 1000 of patches to support our reference hardware [3] and -cip-rt branch, with
>> is merge of -rt and -cip trees.
>>
>> If you for some reason need 4.4.x with bug and security fixes, and are running
>> similar hardware to our reference hardware (x86-64 and armv7), -cip tree may
>> be good base for that work. Testing of the -cip tree is welcome, as is joining the
>> CIP project.
>>
>> [1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
>> [2]
>> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linu
>> x-4.4.y-cip-rt
>> [3]
>> https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/ciprefe
>> rencehardware
> 
> Thank you for taking up the issue. I think the content is fine.

Looks good to me as well.

Given that 4.4 is now history and Greg even mentioned CIP in his
discontinuation message [1] but said that we would only "consider" to
continue: Let's follow up on his post, only referring to the regular
linux-4.4.y-cip for now. Who of you two could do that?

> BTW, do you have any future information about the RT kernel team?
> We may also need to check the RT patch.
> If you don't have the information, I'll ask the RT team about this.
> 

Why should 4.4-rt continue if its former upstream retired?

Jan

[1] https://lkml.org/lkml/2022/2/3/91

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2022-02-06 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 21:32 4.4.302 is going to be last 4.4 release Pavel Machek
2022-02-03  7:13 ` [cip-dev] " nobuhiro1.iwamatsu
2022-02-06 18:47   ` Jan Kiszka [this message]
2022-02-08  9:43     ` Chris Paterson
2022-02-08 15:36       ` Pavel Machek
2022-02-09 11:05         ` Chris Paterson
2022-02-14 21:34           ` Pavel Machek

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=1ac8ef07-4bba-71ef-83da-524c1a717be0@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    /path/to/YOUR_REPLY

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

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