From: "Sunil Naidu" <akula2.shark@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Realtime-preemption for 2.6.20-rc5 ?
Date: Sat, 20 Jan 2007 08:26:40 +0530 [thread overview]
Message-ID: <8355959a0701191856t5cadf684jdabb939d103de020@mail.gmail.com> (raw)
In-Reply-To: <20070118101949.GA22671@elte.hu>
On 1/18/07, Ingo Molnar <mingo@elte.hu> wrote:
> the best place to start is:
>
> http://rt.wiki.kernel.org
>
> Ingo
I did refer the same. Is it necessary to use only base kernel, say
2.6.19? Or, can I go ahead with 2.6.19 + 2.6.19.2 patch + 2.6.19-rt
patch?
If yes, any reason why we need to apply rt patch only to a base kernel?
Thanks,
~Akula2
next prev parent reply other threads:[~2007-01-20 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 10:15 Sunil Naidu
2007-01-18 10:19 ` Ingo Molnar
2007-01-20 2:56 ` Sunil Naidu [this message]
2007-01-20 23:39 Pavel Pisa
2007-01-21 9:10 ` Peter Zijlstra
2007-01-21 12:44 ` Pavel Pisa
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=8355959a0701191856t5cadf684jdabb939d103de020@mail.gmail.com \
--to=akula2.shark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®