From: Julia Cartwright <julia@ni.com>
To: <linux-rt-users@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Kacur <jkacur@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH RT 0/4] Linux 4.1.46-rt52-rc1
Date: Fri, 10 Nov 2017 10:33:22 -0600 [thread overview]
Message-ID: <cover.1510269414.git.julia@ni.com> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 4.1.46-rt52-rc1. Please review
the included patches, and test!
You might ask: "Where was 4.1.46-rt51?". The answer is: it was released
silently, and only as a means to facilitate release-level bisection.
Version 4.1.46-rt51 has known issues to be resolved by the pending
release of -rt52.
The -rc release will be uploaded to kernel.org and will be deleted when the
final release is out. This is just a review release (or release candidate).
The pre-releases will not be pushed to the git repository, only the
final release is.
If all goes well, this patch will be converted to the next main release
on 11/15/2017.
Julia
----------------------------------------------------------------
To build 4.1.46-rt52-rc1 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz
http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.1.46.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/patch-4.1.46-rt52-rc1.patch.xz
You can also build from 4.1.46-rt51 release by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/incr/patch-4.1.46-rt51-rt52-rc1.patch.xz
Julia Cartwright (2):
workqueue: fixup rcu check for RT
Linux 4.1.46-rt52-rc1
Sebastian Andrzej Siewior (2):
PM / CPU: replace raw_notifier with atomic_notifier (fixup)
kernel/hrtimer: migrate deferred timer on CPU down
kernel/cpu_pm.c | 7 +++++++
kernel/time/hrtimer.c | 5 +++++
kernel/workqueue.c | 2 +-
localversion-rt | 2 +-
4 files changed, 14 insertions(+), 2 deletions(-)
--
2.14.2
next reply other threads:[~2017-11-10 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 16:33 Julia Cartwright [this message]
2017-11-10 16:33 ` [PATCH RT 1/4] PM / CPU: replace raw_notifier with atomic_notifier Julia Cartwright
2017-11-10 16:33 ` [PATCH RT 2/4] workqueue: fixup rcu check for RT Julia Cartwright
2017-11-10 16:33 ` [PATCH RT 3/4] kernel/hrtimer: migrate deferred timer on CPU down Julia Cartwright
2017-11-10 16:33 ` [PATCH RT 4/4] Linux 4.1.46-rt52-rc1 Julia Cartwright
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=cover.1510269414.git.julia@ni.com \
--to=julia@ni.com \
--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=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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