From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] 4.4.302 is going to be last 4.4 release
Date: Tue, 8 Feb 2022 16:36:01 +0100 [thread overview]
Message-ID: <20220208153601.GA5021@duo.ucw.cz> (raw)
In-Reply-To: <OSZPR01MB68774ED2525BD5F8B8AE8414B72D9@OSZPR01MB6877.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi!
> > > 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?
>
> Didn't CIP commit to maintaining a real-time version of each SLTS for the 10 years?
We did commit to maintaining 4.4-cip-rt, but upstream 4.4.X is going
to be discontinued, and so is 4.4.X-stable.
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-08 15:36 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
2022-02-08 9:43 ` Chris Paterson
2022-02-08 15:36 ` Pavel Machek [this message]
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=20220208153601.GA5021@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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