From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Julia Cartwright <julia@ni.com>, Daniel Wagner <wagi@monom.org>,
Tom Zanussi <zanussi@kernel.org>,
"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Subject: [ANNOUNCE] 4.19.106-rt44
Date: Fri, 28 Feb 2020 17:08:37 -0500 [thread overview]
Message-ID: <20200228170837.3fe8bb57@gandalf.local.home> (raw)
Dear RT Folks,
I'm pleased to announce the 4.19.106-rt44 stable release.
This release is just an update to the new stable 4.19.106 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v4.19-rt
Head SHA1: 0f2960c75dd68d339f0aff2935f51652b5625fbf
Or to build 4.19.106-rt44 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz
http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.19.106.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/patch-4.19.106-rt44.patch.xz
Enjoy,
-- Steve
next reply other threads:[~2020-02-28 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 22:08 Steven Rostedt [this message]
2020-03-19 21:48 ` [ANNOUNCE] 4.19.106-rt44 Pavel Machek
2020-03-19 23:22 ` 4.19.106-rt44 -- boot problems with irqwork: push most work into softirq context Pavel Machek
2020-03-20 0:48 ` Steven Rostedt
2020-03-20 19:54 ` Pavel Machek
2020-03-20 20:05 ` Steven Rostedt
2020-03-21 22:43 ` Pavel Machek
2020-03-21 23:00 ` Pavel Machek
2020-03-29 10:09 ` 4.4-rt ... seems to have same ireqwork problem was " Pavel Machek
2020-03-30 20:15 ` Steven Rostedt
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=20200228170837.3fe8bb57@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=zanussi@kernel.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;
as well as URLs for NNTP newsgroup(s).