From: jordan <triplesquarednine@gmail.com>
To: Mugunth <mugunthanvnm@gmail.com>
Cc: E-Blokos <infos@e-blokos.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: kernel 2.6.39
Date: Sun, 22 May 2011 14:09:11 -0400 [thread overview]
Message-ID: <BANLkTinAFwEoCkPUV5m1Kf=F1i5AXyi85w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=7HuChAsv2OrsaBsRx2Rtnc4Sn+g@mail.gmail.com>
> Hi Jordan,
hi,
> I am new to RT kernel. I am trying to use 2.6.37 kernel with RT. I am unable
> to succeed.
you are unable to succeed, because there is no 2.6.37-rt available.
last i heard the patchset was being worked on, not actually available
- you must use 2.6.33-rt. that is the last stable release of RT.
> Since you are using 2.6.39 with RT. Are you using any patches which are not
> mainlined in kernel, so that I can also contribute in testing your patches.
AFAIK, I am not using 2.6.39 with RT - i am using 2.6.39 which
includes one of the main features that RT provided. I have the
forced-interrupt-threading - enabled in my kernel (using nconfig
before compiling 2.6.39, to customize my kernel how i wanted it).
I am not an RT maintainer, or even contributor. I do not write patches
and am an end-user. (i use RT, specifically for proaudio on the Linux
platform).
I was just answering E-BLOKOS' question, because it seemed as if he
wasn't aware as to why those commits in 2.6.39 would show bits of code
related to and specific to RT.
jordan
--
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
prev parent reply other threads:[~2011-05-22 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:58 kernel 2.6.39 E-Blokos
2011-05-21 15:08 ` jordan
[not found] ` <BANLkTi=7HuChAsv2OrsaBsRx2Rtnc4Sn+g@mail.gmail.com>
2011-05-22 18:09 ` jordan [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='BANLkTinAFwEoCkPUV5m1Kf=F1i5AXyi85w@mail.gmail.com' \
--to=triplesquarednine@gmail.com \
--cc=infos@e-blokos.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mugunthanvnm@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).