From: Daniel Wagner <wagi@monom.org>
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>,
Daniel Wagner <daniel.wagner@siemens.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Julia Cartwright <julia@ni.com>
Subject: [ANNOUNCE] 4.4.138-rt155
Date: Fri, 22 Jun 2018 10:13:04 +0200 [thread overview]
Message-ID: <20180622081829.BE082500BA9@mail.monom.org> (raw)
Hello RT Folks!
I'm pleased to announce the 4.4.138-rt155 stable release.
This release is just an update to the new stable 4.4.137 version
and no RT specific changes have been made.
As turns out, it is not a ghost I am hunting:
https://ci-rt.linutronix.de/RT-Test/histogram.jsp?cyclictest=517&id=144
So get this spike pops up under load on the CI test farm and also on
my local test computer. Though the only problem is, that it doesn't
show up when tracing is enabled. So if someone gets hold of a trace
please share it!
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: f9dc938fce05dbf24c1a7132cc3248b2799c94b7
Or to build 4.4.138-rt155 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.4.tar.xz
http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.4.138.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4.138-rt155.patch.xz
You can also build from 4.4.137-rt154 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.4/incr/patch-4.4.137-rt154-rt155.patch.xz
Enjoy!
Daniel
reply other threads:[~2018-06-22 8:13 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=20180622081829.BE082500BA9@mail.monom.org \
--to=wagi@monom.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=jkacur@redhat.com \
--cc=julia@ni.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 \
/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).