From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: linux 3.8
Date: Fri, 1 Mar 2013 14:19:44 -0500 [thread overview]
Message-ID: <5130FF50.6070401@windriver.com> (raw)
In-Reply-To: <CA+gsK-qsTjhRnH26Oc5YD++jcgGda4f4kV+CJ3aAJCdkqV=Kng@mail.gmail.com>
On 13-03-01 02:15 PM, Rudolf Streif wrote:
> Bruce,
>
> On Fri, Mar 1, 2013 at 9:29 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
> But note, Greg is talking specifically about LTSI, we don't
> expect more than one LTSI per year, and we are already locked into
> the LTSI 3.4.
>
> However, as far as I understand it the 3.4 snapshot in
> git.yoctoproject.org <http://git.yoctoproject.org> is from kernel.org
> <http://kernel.org> and not from
> http://git.linuxfoundation.org/ltsi-kernel.git. GregKH has been merging
> patches into the LTSI kernel, such as AF_BUS, that have not been
> accepted by upstream. I do not think that those patches are being merged
> into the YP kernel tree. But please correct me if I am wrong.
The 3.4 LTSI patches are all present on the 3.4 kernel tree, directly
from Greg's patch queue.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.4/log/?h=ltsi
And that branch is merged into each and every other branch in the
linux-yocto tree.
We've been involved with Greg and LTSI for quite a while now, and are
tracking it via our tree as we discussed with the interested parties.
Cheers,
Bruce
>
> Cheers,
> Rudi
next prev parent reply other threads:[~2013-03-01 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:42 linux 3.8 Trevor Woerner
2013-03-01 17:29 ` Bruce Ashfield
2013-03-01 19:15 ` Rudolf Streif
2013-03-01 19:19 ` Bruce Ashfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-19 0:28 Linux 3.8 Linus Torvalds
2013-02-19 2:15 ` Stephen Rothwell
2013-02-19 12:14 ` Steven Rostedt
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=5130FF50.6070401@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=rstreif@linuxfoundation.org \
--cc=yocto@yoctoproject.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 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.