public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: 2.6.26.8-rt14
Date: Thu, 29 Jan 2009 00:17:40 -0500	[thread overview]
Message-ID: <1233206260.3833.41.camel@localhost.localdomain> (raw)
In-Reply-To: <1233205779.922.46.camel@localhost.localdomain>

Doh! Fixed subject. I need more sleep.

-- Steve


On Thu, 2009-01-29 at 00:09 -0500, Steven Rostedt wrote:
> We are pleased to announce the 2.6.26.8-rt14 tree which can be
> downloaded from the following 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.6-rt13
> 
>  - don't disable interrupts in ide ata code on RT (Steven Rostedt)
> 
>  - backport hex fix in ftrace (Carsten Emde)
> 
>  - fix trace histogram warn on (Thomas Gleixner)
> 
>  - fix ftrace preempt count recording (Carsten Emde)
> 
>   - disable SCHED_HRTICK (Thomas Gleixner)
> 
>   - fix typo in tasklet_hi_action (Adam Sampson)
> 
> to build the 2.6.26.8-rt14 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.8.bz2
>   http://rt.et.redhat.com/download/patch-2.6.26.8-rt14.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.
> 
> ***************************************************************
> ***************************************************************
> ******  COMING SOON !!! COMING SOON !!! COMING SOON !!! *******
> ******  COMING SOON !!! COMING SOON !!! COMING SOON !!! *******
> ***************************************************************
> ***************************************************************
> 
> The RT git tree is almost ready!  It is currently based off of 2.6.28,
> until it becomes a little more stable. You can down load it now from the
> git repo:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-rt.git
> 
> It boots on x86_64. A few more patches still need to be applied, but the
> majority of them have been incorporated. Work on the non x86 archs also
> needs to be done.
> 
> Once the git tree is pretty stable I will release a 2.6.28-rt1 patch,
> make a v2.6.28-rt branch and then go right in sync with the mainline
> tree.
> 
> Feel free to download it now and give it a try. And you can send me any
> crashes that you see.
> 
> 
> -- Steve
> 
> 
> 


      reply	other threads:[~2009-01-29  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  5:09 2.6.26.8-rt13 Steven Rostedt
2009-01-29  5:17 ` Steven Rostedt [this message]

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=1233206260.3833.41.camel@localhost.localdomain \
    --to=srostedt@redhat.com \
    --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