From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.35 + rt?
Date: Wed, 13 Oct 2010 10:35:41 -0700 [thread overview]
Message-ID: <4CB5EDED.10100@localhost> (raw)
In-Reply-To: <4CB3A520.9040300@ccrma.stanford.edu>
On 10/11/2010 05:00 PM, Fernando Lopez-Lezcano wrote:
> Any news on the above combination? I can test if there is something
> available...
Hmmm, looks like the git repo is tracking 2.6.36 up to rc7. I presume
that is going to be the next "oficial" rt patch (instead of 2.6.35). Is
it usable at this point? Should I try to test? Should I wait?
-- Fernando
next prev parent reply other threads:[~2010-10-13 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 0:00 2.6.35 + rt? Fernando Lopez-Lezcano
2010-10-12 2:00 ` Madovsky
2010-10-13 17:35 ` Fernando Lopez-Lezcano [this message]
2010-10-14 20:33 ` Frank Rowand
2010-10-14 21:07 ` Fernando Lopez-Lezcano
2010-10-14 22:02 ` Frank Rowand
2010-10-14 22:12 ` Fernando Lopez-Lezcano
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=4CB5EDED.10100@localhost \
--to=nando@ccrma.stanford.edu \
--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).