From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: [ANNOUNCE] 3.2-rc1-rt1
Date: Sun, 13 Nov 2011 23:57:50 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1111132213220.2694@ionos> (raw)
Dear RT Folks,
I'm pleased to announce the 3.2-rc1-rt1 release.
It's a straight forward port of the 3.0-rt patch queue, which reduced
the patch size by more than 25% from 807k to 580k. The diffstat change
is:
429 files changed, 10118 insertions(+), 3000 deletions(-)
318 files changed, 8871 insertions(+), 1858 deletions(-)
Thanks to all who helped polishing patches and bringing them mainline!
The test results on my reference machine are in the 3.0-rt ballpark
and I have not seen any frightening explosions so far.
3.2-rc1-rt is not against 3.2-rc1 - it's against the post rc1
commit 52e4c2a05256cb83cda12f3c2137ab1533344edb.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=52e4c2a05256cb83cda12f3c2137ab1533344edb
For non git users conveniance I uploaded a delta patch against
3.2-rc1:
https://tglx.de/~tglx/rt/3.2/base/patch-3.2-rc1-52e4c2a05-rt1.patch.gz
to get the base kernel on which the RT patch applies.
The RT patch against 3.2-rc1-52e4c2a05 can be found here:
https://tglx.de/~tglx/rt/3.2/patch-3.2-rc1-52e4c2a05-rt1.patch.gz
The split quilt queue is available at:
https://tglx.de/~tglx/rt/3.2/patches-3.2-rc1-52e4c2a05-rt1.tar.gz
Enjoy,
tglx
next reply other threads:[~2011-11-13 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 22:57 Thomas Gleixner [this message]
2011-11-14 9:14 ` [ANNOUNCE] 3.2-rc1-rt1 - Compile errors also for rc1 vanilla Tim Sander
2011-11-14 10:00 ` Thomas Gleixner
2011-11-14 11:46 ` Heinz Diehl
2011-11-14 12:58 ` jordan
2011-11-14 16:57 ` Steven Rostedt
2011-11-21 17:30 ` Steven Rostedt
2011-11-21 17:30 ` Steven Rostedt
2011-11-22 9:34 ` Tim Sander
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=alpine.LFD.2.02.1111132213220.2694@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/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.