From: Frank Rowand <frank.rowand@am.sony.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: <tglx@linutronix.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.35 + rt?
Date: Thu, 14 Oct 2010 15:02:11 -0700 [thread overview]
Message-ID: <4CB77DE3.40904@am.sony.com> (raw)
In-Reply-To: <4CB77122.40408@localhost>
On 10/14/10 14:07, Fernando Lopez-Lezcano wrote:
> On 10/14/2010 01:33 PM, Frank Rowand wrote:
>> On 10/13/10 10:35, Fernando Lopez-Lezcano wrote:
>>> 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
>> Which branch of which repo is that?
>
> From here:
> https://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch#Download
>
> I go to:
> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=summary
OK, branch master is 2.6.37-rc7 (according to Makefile), but the various
rt branches that I looked at are not. Branch master does not appear to
contain the RT patches.
There are a lot of different rt branches, and I did not look
at all of them, but I looked at several obvious possibilities.
As of the 2.6.22-rt3 announcement, branch rt/head was going to follow the linus tree
but is currently 2.6.33-rt (according to Makefile), and was last modified March 3.
Branch rt/2.6.33 is currently 2.6.33.7.1-rt29, last modified Sept 16.
The other rt branches I looked at are older.
So it looks to me like the latest RT development in git is currently at
2.6.33.7 plus a few changes. Am I understanding this correctly?
Thanks,
Frank
next prev parent reply other threads:[~2010-10-14 22:02 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
2010-10-14 20:33 ` Frank Rowand
2010-10-14 21:07 ` Fernando Lopez-Lezcano
2010-10-14 22:02 ` Frank Rowand [this message]
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=4CB77DE3.40904@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.