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 0/6] [ANNOUNCE] v3.0.9-rt26-rc2
Date: Mon, 21 Nov 2011 16:44:20 -0500 [thread overview]
Message-ID: <20111121214420.124907956@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
Dear RT Folks,
This is the RT stable review cycle. As I am just starting to manage the
3.0-rt stable tree, I'm in the process of creating scripts and such to
send out patches. I will always send out a -rc1 to give people a chance
to yell at me for something stupid I did. It will also allow others
to run this under their own tests as I have a limited testing that I do.
The -rc release will be uploaded to kernel.org and will be deleted when
a new release is out. This is just a review release (or release candidate).
I will also be updating the git tree on kernel.org with the final release
but the pre releases will not be in the public tree. The final release
will also include the full broken out patches.
to build a 3.0.9-rt26-rc2 tree, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.xz
http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.9.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/patch-3.0.9-rt26-rc2.patch.xz
You can also build from 3.0.9-rt25 by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/incr/patch-3.0.9-rt25-rt26-rc2.patch.xz
If all goes well, this patch will be converted to the main release
next Tuesday: 11/22/2011
The differences between -rc1 and -rc2 is:
Added two Reviewed-by tags from Paul McKenney.
Added the tracing patch that was added in v3.2-rc2-rt3
Enjoy,
-- Steve
John Kacur (2):
softirq: Export in_serving_softirq()
rcu: Fix macro substitution for synchronize_rcu_bh() on RT
Peter Zijlstra (1):
x86: crypto: Reduce preempt disabled regions
Steven Rostedt (2):
tracing: Show padding as unsigned short
Linux 3.0.9-rt26-rc2
Thomas Gleixner (1):
dm: Make rt aware
----
arch/x86/crypto/aesni-intel_glue.c | 24 +++++++++++++-----------
drivers/md/dm.c | 4 ++--
include/linux/rcutree.h | 2 +-
kernel/softirq.c | 1 +
kernel/trace/trace_events.c | 2 +-
localversion-rt | 2 +-
6 files changed, 19 insertions(+), 16 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-11-21 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 21:44 Steven Rostedt [this message]
2011-11-21 21:44 ` [PATCH 1/6] softirq: Export in_serving_softirq() Steven Rostedt
2011-11-21 21:44 ` [PATCH 2/6] rcu: Fix macro substitution for synchronize_rcu_bh() on RT Steven Rostedt
2011-11-21 21:44 ` [PATCH 3/6] x86: crypto: Reduce preempt disabled regions Steven Rostedt
2011-11-21 21:44 ` [PATCH 4/6] dm: Make rt aware Steven Rostedt
2011-11-21 21:44 ` [PATCH 5/6] tracing: Show padding as unsigned short Steven Rostedt
2011-11-21 21:44 ` [PATCH 6/6] Linux 3.0.9-rt26-rc2 Steven Rostedt
2011-11-22 8:36 ` [PATCH 0/6] [ANNOUNCE] v3.0.9-rt26-rc2 Tim Sander
2011-11-22 13:26 ` Steven Rostedt
2011-11-22 13:26 ` 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=20111121214420.124907956@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.