From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: dvhart@linux.intel.com, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto: update base to v3.0.8 + meta config changes
Date: Thu, 03 Nov 2011 19:15:55 +0000 [thread overview]
Message-ID: <1320347755.20107.72.camel@ted> (raw)
In-Reply-To: <CADkTA4PyZ7r7aiGpENv1RSygtj-ni53XFOBPqOhETruUqem+Ew@mail.gmail.com>
On Thu, 2011-11-03 at 14:12 -0400, Bruce Ashfield wrote:
> On Thu, Nov 3, 2011 at 2:07 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >
> > Op 3 nov. 2011, om 18:53 heeft Bruce Ashfield het volgende geschreven:
> >
> >> On Thu, Nov 3, 2011 at 1:22 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>>
> >>> Op 3 nov. 2011, om 18:11 heeft Bruce Ashfield het volgende geschreven:
> >>>
> >>>> Richard/Saul,
> >>>>
> >>>> Here's a bump to 3.0.8 for the 3.0 kernel, and some config changes from TomZ.
> >>>> These are destined for master and separate from any point updates to the 1.1
> >>>> release.
> >>>>
> >>>> In case anyone cares my -dev kernel also has these changes, and it will take
> >>>> them to the latest kernel shortly.
> >>>>
> >>>> This also doesn't bump the preempt-rt branches, since they'll be updated
> >>>> to the new -rt first, before taking the 3.0.x stable updates.
> >>>>
> >>>> Built and booted for all the qemu targets.
> >>>>
> >>>> cc: Tom Zanussi <tom.zanussi@intel.com>
> >>>> cc: Darren Hart <dvhart@linux.intel.com>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Bruce
> >>>>
> >>>> The following changes since commit 9b76e6a2cfc5a4d779f3b06e3acc5ff7b8275470:
> >>>>
> >>>> meta: glib-2.0: don't apply qsort_r test removable patch for native version (2011-11-02 09:08:28 +0000)
> >>>>
> >>>> are available in the git repository at:
> >>>> git://git.pokylinux.org/poky-contrib zedd/kernel
> >>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
> >>>
> >>> Do you also have a tree against oe-core?
> >>
> >> I don't have a contrib branch, I asked a few week ago, but still don't have it
> >> created. So I have a tree, but no where to push submissions.
> >
> > Forking https://github.com/openembedded/oe-core is easy enough :)
>
> Sure. But I dislike github in general (everyone has their preferences) and was
> trying to get a contrib branch. There's a myriad of machines I could use for it
> as well, but I see no reason for a contrib branch to be hard to get,
> so I'm waiting
> for the moment and focusing on getting some kernel work done.
I also have a dislike of github. Are you after access to
openembedded-core-contrib? I can sort that out...
Cheers,
Richard
next prev parent reply other threads:[~2011-11-03 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 17:11 [PATCH 0/1] linux-yocto: update base to v3.0.8 + meta config changes Bruce Ashfield
2011-11-03 10:22 ` Darren Hart
2011-11-03 17:51 ` Bruce Ashfield
2011-11-03 17:11 ` [PATCH 1/1] linux-yocto_3.0: " Bruce Ashfield
2011-11-03 17:22 ` [PATCH 0/1] linux-yocto: " Koen Kooi
2011-11-03 17:53 ` Bruce Ashfield
2011-11-03 18:07 ` Koen Kooi
2011-11-03 18:12 ` Bruce Ashfield
2011-11-03 19:15 ` Richard Purdie [this message]
2011-11-03 23:52 ` Bruce Ashfield
2011-11-07 17:46 ` Saul Wold
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=1320347755.20107.72.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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 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.