From: Chirag Jog <chirag@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.26.5-rt8
Date: Wed, 10 Sep 2008 12:25:20 +0530 [thread overview]
Message-ID: <20080910065520.GC3966@linux.vnet.ibm.com> (raw)
In-Reply-To: <1221018492.22713.24.camel@localhost.localdomain>
* Steven Rostedt <rostedt@goodmis.org> [2008-09-09 23:48:12]:
> We are pleased to announce the 2.6.26.5-rt8 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.26.3-rt7
>
> - Ported to 2.6.26.5
>
> - x86_32 tlb flush use raw spinlock (Chirag Jog)
>
> - seqlock fix non PREEMPT_RT and cleanup (Steven Rostedt)
>
> - add sysctl to warn on RT task using not PI futex (Steven Rostedt)
>
> to build a 2.6.26.5-rt8 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.26.5.bz2
> http://rt.et.redhat.com/download/patch-2.6.26.3-rt8.bz2
This link ^^ is incorrect.
Correct one is :
http://rt.et.redhat.com/download/patch-2.6.26.5-rt8.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
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-Thanks,Chirag
next prev parent reply other threads:[~2008-09-10 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 3:48 2.6.26.5-rt8 Steven Rostedt
2008-09-10 6:55 ` Chirag Jog [this message]
2008-09-10 11:31 ` 2.6.26.5-rt8 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=20080910065520.GC3966@linux.vnet.ibm.com \
--to=chirag@linux.vnet.ibm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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.