From: Daniel Wagner <dwagner@suse.de>
To: 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: [ANNOUNCE] 4.4.262-rt219
Date: Sat, 20 Mar 2021 16:25:35 -0000 [thread overview]
Message-ID: <161625753552.20205.6230905513724868931@beryllium> (raw)
Hello RT-list!
I'm pleased to announce the 4.4.262-rt219 stable release.
This is just an update to the latest stable release. No RT
specific changes.
I tried to fix the locking self failures I reported last time. As it
turns out the test setup was somehow broken. After redoing all the
test just using 'defconfig + kvmconfig + locking_selftest' all worked
fine. I also tested older v4.4-rt releases and there was no failures.
Furthermore, the cyclicdeadline fails again, which I probably a good
thing; I don't believe in self healing capabilities of the -rt patchset.
Anyway, I think my build/test setup was just broken.
Known issue:
- locktorture reports a might_sleep warning for spin_locks test
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.4-rt
Head SHA1: d18d08f6afe25c27207d26a9811e23abf7ef36b8
Or to build 4.4.262-rt219 directly, the following patches should be applied:
https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.4.tar.xz
https://www.kernel.org/pub/linux/kernel/v4.x/patch-4.4.262.xz
https://www.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4.262-rt219.patch.xz
Enjoy!
Daniel
reply other threads:[~2021-03-20 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=161625753552.20205.6230905513724868931@beryllium \
--to=dwagner@suse.de \
--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=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;
as well as URLs for NNTP newsgroup(s).