From: Mark Knecht <markknecht@gmail.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 2.6.33.9-rt31
Date: Mon, 11 Apr 2011 09:59:39 -0700 [thread overview]
Message-ID: <BANLkTinAuGJxScO5nO1+gB_OmK43xTtEbg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104111723020.4501@localhost6.localdomain6>
On Mon, Apr 11, 2011 at 8:35 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> We are pleased to announce the next update to our new preempt-rt
> series which is mostly a forward to 2.6.33.9. Thanks Greg !
>
> RT specific patches since 2.6.33.7.2-rt30
As always, thanks for the work you all do on this kernel.
I have a machine that requires drivers circa 2.6.37 or later, which
happened to be what was announced as the next future preempt-rt
kernel. At this point I'm using a standard 2.6.38 kernel and getting
pretty good results, and with more and more of the preempt-rt stuff
going mainline all the time, what's the roadmap for preempt-rt going
forward?
Thanks,
Mark
next prev parent reply other threads:[~2011-04-11 16:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 15:35 [ANNOUNCE] 2.6.33.9-rt31 Thomas Gleixner
2011-04-11 15:42 ` Madovsky
2011-04-11 16:06 ` Thomas Gleixner
2011-04-11 16:19 ` Oon-Ee Ng
2011-04-11 16:36 ` Carsten Emde
2011-04-11 16:46 ` Thomas Gleixner
2011-04-13 17:51 ` Madovsky
2011-04-13 18:38 ` jordan
2011-04-13 18:54 ` Jeremy Jongepier
2011-04-13 21:13 ` jordan
2011-04-13 23:38 ` Niccolò Belli
2011-04-14 7:02 ` Jeremy Jongepier
2011-04-14 7:26 ` jordan
2011-04-14 7:42 ` Jeremy Jongepier
2011-04-14 15:58 ` Madovsky
2011-04-14 22:14 ` jordan
2011-04-15 8:22 ` Tracey Hytry
2011-04-17 16:26 ` Niccolò Belli
2011-04-15 15:02 ` dashesy
2011-04-16 8:35 ` Jeremy Jongepier
2011-05-03 23:16 ` dashesy
2011-04-11 16:59 ` Mark Knecht [this message]
2011-04-11 19:23 ` Uwe Kleine-König
2011-04-11 22:57 ` Mark Knecht
2011-04-13 11:02 ` Jeremy Jongepier
2011-04-13 13:39 ` Jan Kiszka
2011-04-13 15:19 ` Jeremy Jongepier
2011-04-18 15:08 ` Clark Williams
2011-04-18 19:14 ` Jan Kiszka
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=BANLkTinAuGJxScO5nO1+gB_OmK43xTtEbg@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-rt-users@vger.kernel.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 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).