Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto: update base to v3.0.8 + meta config changes
Date: Thu, 3 Nov 2011 13:51:41 -0400	[thread overview]
Message-ID: <4EB2D4AD.4020005@windriver.com> (raw)
In-Reply-To: <4EB26B6B.7050600@linux.intel.com>

On 11-11-03 06:22 AM, Darren Hart wrote:
>
>
> On 11/03/2011 10:11 AM, Bruce Ashfield wrote:
>> 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.
>>
>
> So typically we try to push to master and pull back to the point
> releases. The linux-yocto infrastructure is a bit unique - how will you
> be presenting the stable update and the preempt-rt update (you mentioned
> below) for the point release?

We created the 3.0-1.1.x repo to gather point updates, so yes,
it is a variant on a branch and the same workflow. For changes
that are in both, it is a push and pull (i.e. 3.0.8) into that
repository. If it isn't destined for both, it goes into the 3.0
repo and never appears in the 3.0-1.1.x repository. But nothing
will appear in a point release that isn't already in master.

Cheers,

Bruce


>
> --
> Darren
>
>> 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
>>
>> Bruce Ashfield (1):
>>    linux-yocto_3.0: update base to v3.0.8 + meta config changes
>>
>>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    2 +-
>>   meta/recipes-kernel/linux/linux-yocto_3.0.bb    |   18 +++++++++---------
>>   2 files changed, 10 insertions(+), 10 deletions(-)
>>
>




  reply	other threads:[~2011-11-03 17:58 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 [this message]
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
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=4EB2D4AD.4020005@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox