From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 4.4.302
Date: Thu, 17 Feb 2022 21:55:50 +0100 [thread overview]
Message-ID: <20220217205550.GA21004@duo.ucw.cz> (raw)
In-Reply-To: <1643877137240249@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
Hi!
> I'm announcing the release of the 4.4.302 kernel.
>
> This kernel branch is now END-OF-LIFE. It will not be getting any more
> updates from the kernel stable team, and will most likely quickly become
> insecure and out-of-date. Do not use it anymore unless you really know
> what you are doing.
>
> Note, the CIP project at https://www.cip-project.org/ is considering to
> maintain the 4.4 branch in a limited capability going forward. If you
> really need to use this kernel version, please contact them.
Yes, please; feel free to contact us.
Greg, we'll likely keep maintaining "stable 4.4.X" separately from
"stable + changes for cip hardware, aka 4.4.X-cipY". Would it be okay
if we simply kept tagging those kernels as 4.4.303 / 4.4.304 / ...?
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=linux-4.4.y-cip-rt
[3] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
?
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 --]
next prev parent reply other threads:[~2022-02-17 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:46 Greg Kroah-Hartman
2022-02-03 8:46 ` Greg Kroah-Hartman
2022-02-17 20:55 ` Pavel Machek [this message]
2022-02-18 6:42 ` Greg Kroah-Hartman
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=20220217205550.GA21004@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®