From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>, RT <linux-rt-users@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: 2.6.24-rc7-rt2
Date: Mon, 14 Jan 2008 13:41:20 -0500 [thread overview]
Message-ID: <1200336080.318.8.camel@localhost.localdomain> (raw)
We are pleased to announce the 2.6.24-rc7-rt2 tree, which can be
downloaded from the location:
http://rt.et.redhat.com/download/
Information on the RT patch can be found at:
http://rt.wiki.kernel.org/index.php/Main_Page
Changes since 2.6.24-rc7-rt1
- Several merge fixes reported by:
Mariusz Kozloski
- Removal of kvm-rt.patch (it's so old it is now bogus)
- PPC compile fix (reported by: Robert Schwebel)
- Remove of running softirq by hardirq (too dangerous)
- Changed BUG_ON in filemap from atomic to pagefault disabled
(Steven Rostedt)
Note: There are still some fixes that are not incorporated here yet.
to build a 2.6.24-rc7-rt2 tree, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2
http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.24-rc7.bz2
http://rt.et.redhat.com/download/patch-2.6.24-rc7-rt2.bz2
And like always, my RT version of Matt Mackall's ketchup will get this
for you nicely:
http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
The broken out patches are also available.
-- Steve
next reply other threads:[~2008-01-14 18:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 18:41 Steven Rostedt [this message]
2008-01-14 20:02 ` 2.6.24-rc7-rt2 Mark Knecht
2008-01-14 22:16 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-14 22:30 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 17:10 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 2:07 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:11 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 17:25 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:57 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-15 0:37 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 3:50 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 4:04 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 6:23 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 14:12 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 16:22 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-21 11:31 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-21 12:49 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-27 21:51 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-28 2:32 ` 2.6.24-rc7-rt2 Stefan Monnier
2008-01-16 13:17 ` 2.6.24-rc7-rt2 Alan Cox
2008-01-16 4:01 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 7:12 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 10:11 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-17 2:20 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 3:44 ` 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz() Mike Galbraith
2008-01-15 16:27 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-15 18:06 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 20:04 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-16 12:03 ` 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32 Luotao Fu
2008-01-17 3: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=1200336080.318.8.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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