linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Philippe Midol-Monnet <pmidolmonnet@sopragroup.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: RT patch for 2.6.34?
Date: Tue, 11 Jan 2011 17:33:41 -0800	[thread overview]
Message-ID: <4D2D04F5.40200@linux.intel.com> (raw)
In-Reply-To: <8988_1294150773_4D232C75_8988_10048783_1_4D232C74.1080309@sopragroup.com>

On 01/04/2011 06:19 AM, Philippe Midol-Monnet wrote:
> Hello
>
> I have to use kernel 2.6.34-6 (for PPC) and I need the RT patch. Do you
> know if there is an easy way to apply the RT patch to this kernel version?

There is a version floating around, but it hasn't received the stamp of 
approval from tglx, mingo, or rostedt. A review is pending, and others 
are working to polish it up.

I'm working on integrating this into the Yocto Project. I'll post here 
when that is all available.


-- 
Darren Hart
Yocto Linux Kernel

      reply	other threads:[~2011-01-12  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 14:19 RT patch for 2.6.34? Philippe Midol-Monnet
2011-01-12  1:33 ` Darren Hart [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=4D2D04F5.40200@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pmidolmonnet@sopragroup.com \
    /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;
as well as URLs for NNTP newsgroup(s).