From: Steven Rostedt <rostedt@goodmis.org>
To: 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>
Subject: [PATCH RT 0/8] [ANNOUNCE] 3.2.22-rt35-rc1 stable review
Date: Thu, 12 Jul 2012 19:18:27 -0400 [thread overview]
Message-ID: <20120712231827.084920483@goodmis.org> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 3.2.22-rt35-rc1.
Please scream at me if I messed something up. Please test the patches too.
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 7/16/2012.
Enjoy,
-- Steve
To build 3.2.22-rt35-rc1 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.tar.xz
http://www.kernel.org/pub/linux/kernel/v3.x/patch-3.2.22.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/3.2/patch-3.2.22-rt35-rc1.patch.xz
You can also build from 3.2.22-rt34 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.2/incr/patch-3.2.22-rt34-rt35-rc1.patch.xz
Changes from 3.2.22-rt34:
---
Carsten Emde (4):
Latency histogramms: Cope with backwards running local trace clock
Latency histograms: Adjust timer, if already elapsed when programmed
Disable RT_GROUP_SCHED in PREEMPT_RT_FULL
Latency histograms: Detect another yet overlooked sharedprio condition
Mike Galbraith (1):
fs, jbd: pull your plug when waiting for space
Steven Rostedt (1):
Linux 3.2.22-rt35-rc1
Thomas Gleixner (1):
slab: Prevent local lock deadlock
Yong Zhang (1):
perf: Make swevent hrtimer run in irq instead of softirq
----
fs/jbd/checkpoint.c | 2 ++
include/linux/hrtimer.h | 3 ++
include/linux/sched.h | 2 +-
init/Kconfig | 1 +
kernel/events/core.c | 1 +
kernel/hrtimer.c | 16 ++++++++--
kernel/trace/latency_hist.c | 74 +++++++++++++++++++++++--------------------
localversion-rt | 2 +-
mm/slab.c | 26 ++++++++++++---
9 files changed, 85 insertions(+), 42 deletions(-)
next reply other threads:[~2012-07-12 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 23:18 Steven Rostedt [this message]
2012-07-12 23:18 ` [PATCH RT 1/8] Latency histogramms: Cope with backwards running local trace clock Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 2/8] Latency histograms: Adjust timer, if already elapsed when programmed Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 3/8] Disable RT_GROUP_SCHED in PREEMPT_RT_FULL Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 4/8] Latency histograms: Detect another yet overlooked sharedprio condition Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 5/8] slab: Prevent local lock deadlock Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 6/8] fs, jbd: pull your plug when waiting for space Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 7/8] perf: Make swevent hrtimer run in irq instead of softirq Steven Rostedt
2012-07-12 23:18 ` [PATCH RT 8/8] Linux 3.2.22-rt35-rc1 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=20120712231827.084920483@goodmis.org \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).