From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
george anzinger <george@mvista.com>,
Karsten Wiese <annabellesgarden@yahoo.de>,
dwalker@mvista.com
Subject: 2.6.13-rc6-rt1
Date: Tue, 16 Aug 2005 10:41:17 +0200 [thread overview]
Message-ID: <20050816084116.GA16772@elte.hu> (raw)
In-Reply-To: <20050815111804.GA26161@elte.hu>
i've released the 2.6.13-rc6-rt1 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
as the name already suggests, i've switched to a new, simplified naming
scheme, which follows the usual naming convention of trees tracking the
mainline kernel. The numbering will be restarted for every new upstream
kernel the -RT tree is merged to.
the 2.6.13-rc6-rt1 release includes a number of fixes. Changes since
-53-11:
- more HRT fixes (Thomas Gleixner)
- more RCU-tasklist-lock fixes (Paul E. McKenney)
- IPC message-queue and IPC messages wakeup fixes (Daniel Walker)
- VIA VT8237 southbridge quirks to fix IOAPIC issues (Karsten Wiese)
- NMI preemption-count fix (George Anzinger)
- various latency tracer fixes: lost trace entries, SMP weirdnesses (me)
to build a 2.6.13-rc6-rt1 tree, the following patches should to be
applied:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.tar.bz2
http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.13-rc6.bz2
http://redhat.com/~mingo/realtime-preempt/patch-2.6.13-rc6-rt1
Ingo
next prev parent reply other threads:[~2005-08-16 8:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 11:00 [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.53-01, High Resolution Timers & RCU-tasklist features Ingo Molnar
2005-08-12 3:07 ` Lee Revell
2005-08-12 3:19 ` Lee Revell
2005-08-12 7:03 ` Ingo Molnar
2005-08-12 7:48 ` Thomas Gleixner
2005-08-12 7:07 ` Ingo Molnar
2005-08-13 0:28 ` Ryan Brown
2005-08-13 0:32 ` Lee Revell
2005-08-13 0:57 ` George Anzinger
2005-08-14 2:12 ` Ingo Molnar
2005-08-15 6:29 ` Ingo Molnar
2005-08-15 23:39 ` George Anzinger
2005-08-16 6:36 ` Thomas Gleixner
2005-08-15 11:18 ` [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11 Ingo Molnar
2005-08-15 20:35 ` Peter Zijlstra
2005-08-16 3:53 ` Ingo Molnar
2005-08-16 14:35 ` Alan Stern
2005-08-16 16:12 ` Ingo Molnar
2005-08-16 16:56 ` Alan Stern
2005-08-16 17:02 ` Ingo Molnar
2005-08-17 2:23 ` David Brownell
2005-08-17 14:10 ` Alan Stern
2005-08-17 20:51 ` David Brownell
2005-08-18 4:52 ` Ingo Molnar
2005-08-18 6:37 ` David Brownell
2005-08-18 14:43 ` Alan Stern
2005-08-22 11:07 ` Ingo Molnar
2005-08-17 6:31 ` Ingo Molnar
2005-08-16 8:41 ` Ingo Molnar [this message]
2005-08-16 12:32 ` 2.6.13-rc6-rt1 Michal Schmidt
2005-08-27 1:15 ` 2.6.13-rc6-rt1 Matt Mackall
2005-08-29 22:36 ` 2.6.13-rc6-rt1 Esben Nielsen
2005-08-17 0:53 ` [patch] KGDB for Real-Time Preemption systems George Anzinger
2005-08-17 6:53 ` Ingo Molnar
2005-08-17 19:16 ` George Anzinger
2005-09-05 12:23 ` Serge Noiraud
2005-09-08 0:37 ` George Anzinger
2005-09-07 8:55 ` Serge Noiraud
2005-09-07 21:16 ` George Anzinger
2005-09-08 8:57 ` Serge Noiraud
2005-09-08 20:47 ` George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 9:56 2.6.13-rc6-rt1 Milan Svoboda
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=20050816084116.GA16772@elte.hu \
--to=mingo@elte.hu \
--cc=annabellesgarden@yahoo.de \
--cc=dwalker@mvista.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--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