From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Wagner <wagi@monom.org>
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.301-rt231
Date: Wed, 2 Feb 2022 09:25:57 +0100 [thread overview]
Message-ID: <YfpAFdoZ/t74kt7H@kroah.com> (raw)
In-Reply-To: <da5b0bc4-0980-5193-cb65-c1b06e46574b@monom.org>
On Wed, Feb 02, 2022 at 08:56:36AM +0100, Daniel Wagner wrote:
> On 01.02.22 17:14, Daniel Wagner wrote:
> > Hello RT-list!
> >
> > I'm pleased to announce the 4.4.301-rt231 stable release.
> >
> > This is just an update to the latest and last 4.4.x stable
> > release. There are no RT specific changes.
> >
> > With this release there wont be any updates for this branch in
> > stable-rt tree. I understand Pavel Machek is continuing to maintaining
> > the v4.4-rt branch under the CIP umbrella:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt
> >
>
> It seems Greg is still updating v4.4.y. I'll do another update, when 4.4.y
> gets an update
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=linux-4.4.y
I will do one more release, probably in a day or so, and then it is
dead. Run away!!! :)
prev parent reply other threads:[~2022-02-02 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 16:14 [ANNOUNCE] 4.4.301-rt231 Daniel Wagner
2022-02-02 7:56 ` Daniel Wagner
2022-02-02 8:25 ` Greg Kroah-Hartman [this message]
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=YfpAFdoZ/t74kt7H@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=wagi@monom.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox