From: Pavel Machek <pavel@denx.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
Pavel Machek <pavel@denx.de>
Subject: Re: [ANNOUNCE] 4.4.277-rt224
Date: Fri, 20 Aug 2021 19:53:01 +0200 [thread overview]
Message-ID: <20210820175301.GA4791@amd> (raw)
In-Reply-To: <20210820110716.zmh7te5dvmndssgm@carbon.lan>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Hi!
> > > Sorry for the long delay. I was refactoring and improving my test
> > > setup which took a bit longer than I expected. I switched from a
> > > Debian based rootfs to an Tumbleweed based one, for obvious
> > > reasons. Anyway, this should not matter at all.
> >
> > A bit late thanks for the release, BTW. We are maintaining -cip-rt
> > based kernels, and were getting worried :-).
>
> Sorry about that. I should have send out a note earlier. Anyway, I'll
> plan to work on the next update soon. There are a few futex changes
> which collide. It's going to be interesting.
FYI we are on 2 month cycle for -cip-rt, so we are still fine for a
while. We had trouble coordinating matching -cip and -rt releases, but
we decided to adjust -cip cycle to match -rt, so that should be solved.
> BTW, as you certainly are aware, the v4.4 kernel is EOL soon. As I
> understand the CIP is going to take over the maintenance. So I assume
> you are going to care of the -rt version as well?
We are aware, but I don't think we decided what will happen at that
point (and I can't really speak for the project). We plan to maintain
-cip and -cip-rt variants till 2027:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
Taking over -stable and -stable-rt maintainance, too, is something
that may make sense (and we probably will be considered), but it is
likely CIP Technical Steering Committee's (“TSC”) decision.
https://www.cip-project.org/about/charter
Actually, your input may be important here. If you (or SuSE or someone
else) can put some resources into 4.4-rt after February 2022, that
would be good to know.
Best regards,
Pavel
(Again I don't speak for the project)
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-08-20 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 6:39 [ANNOUNCE] 4.4.277-rt224 Daniel Wagner
2021-08-20 10:43 ` Pavel Machek
2021-08-20 11:07 ` Daniel Wagner
2021-08-20 17:53 ` Pavel Machek [this message]
2021-08-26 8:42 ` Daniel Wagner
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=20210820175301.GA4791@amd \
--to=pavel@denx.de \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.