From: John Kacur <jkacur@gmail.com>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.32 rt patch?
Date: Wed, 7 Apr 2010 09:57:57 +0200 [thread overview]
Message-ID: <i2h520f0cf11004070057n2d4e2445l63c7bee944e463d9@mail.gmail.com> (raw)
In-Reply-To: <v2he6bf505b1004061932s2f47ba37q8d80de9af4a14533@mail.gmail.com>
On Wed, Apr 7, 2010 at 4:32 AM, Xianghua Xiao <xiaoxianghua@gmail.com> wrote:
> It seems a few popular distributions will be locked to 2.6.32, is it
> possible to have a 2.6.32-rt?
>
> Xianghua
Dropping a 2.6.33 based kernel on a 2.6.32-based distro is unlikely to
cause any problems.
next prev parent reply other threads:[~2010-04-07 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 2:32 2.6.32 rt patch? Xianghua Xiao
2010-04-07 7:57 ` John Kacur [this message]
2010-04-07 13:59 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2010-04-10 20:47 Nikita V. Youshchenko
2010-04-12 7:43 ` Thomas Gleixner
2010-04-12 19:09 ` Sven-Thorsten Dietrich
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=i2h520f0cf11004070057n2d4e2445l63c7bee944e463d9@mail.gmail.com \
--to=jkacur@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=xiaoxianghua@gmail.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).