All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [PATCH 0/2] linux-yocto: consolidated pull request
Date: Thu, 27 Jan 2011 17:29:58 -0800	[thread overview]
Message-ID: <4D421C16.2070308@intel.com> (raw)
In-Reply-To: <cover.1295905272.git.bruce.ashfield@windriver.com>

On 01/24/2011 01:46 PM, Bruce Ashfield wrote:
> Saul/Richard,
>
> I'm batching two changes that I've been testing together.
>
> The first is explained by the patch itself, but basically it
> allows us to map multiple BSPs onto a single branch for building.
> There's no impact to existing BSPs, but as we go forward it means
> that if boards only differ by configuration we can avoid branch
> explosion in the kernel repo and pickup their different
> configurations. If at any point we need to break them out from
> using a common branch, that is an easy switch to do. I've been
> testing this with a test enablement of the atom-pc using the
> yocto/standar/base branch .. and it works nicely.
>
> The second is an update to pickup Tom's patches for the emenlow.
> Tom will follow up with changes to have the emenlow use the
> 2.6.37 kernel as well as the 2.6.34 kernel.
>
> These are based on top of the beagleboard commits I sent on
> Friday, which I've heard are working their way through the
> queue.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (2):
>    linux-yocto: allow multiple BSPs per branch
>    linux-yocto: update SRCREVs for emenlow
>
>   meta/classes/kernel-yocto.bbclass                  |    4 ++--
>   .../conf/distro/include/poky-default-revisions.inc |    6 +++---
>   .../kern-tools/kern-tools-native_git.bb            |    2 +-
>   3 files changed, 6 insertions(+), 6 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Oops, both where pulled

Sau!



WARNING: multiple messages have this Message-ID (diff)
From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [poky] [PATCH 0/2] linux-yocto: consolidated pull request
Date: Thu, 27 Jan 2011 17:29:58 -0800	[thread overview]
Message-ID: <4D421C16.2070308@intel.com> (raw)
In-Reply-To: <cover.1295905272.git.bruce.ashfield@windriver.com>

On 01/24/2011 01:46 PM, Bruce Ashfield wrote:
> Saul/Richard,
>
> I'm batching two changes that I've been testing together.
>
> The first is explained by the patch itself, but basically it
> allows us to map multiple BSPs onto a single branch for building.
> There's no impact to existing BSPs, but as we go forward it means
> that if boards only differ by configuration we can avoid branch
> explosion in the kernel repo and pickup their different
> configurations. If at any point we need to break them out from
> using a common branch, that is an easy switch to do. I've been
> testing this with a test enablement of the atom-pc using the
> yocto/standar/base branch .. and it works nicely.
>
> The second is an update to pickup Tom's patches for the emenlow.
> Tom will follow up with changes to have the emenlow use the
> 2.6.37 kernel as well as the 2.6.34 kernel.
>
> These are based on top of the beagleboard commits I sent on
> Friday, which I've heard are working their way through the
> queue.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (2):
>    linux-yocto: allow multiple BSPs per branch
>    linux-yocto: update SRCREVs for emenlow
>
>   meta/classes/kernel-yocto.bbclass                  |    4 ++--
>   .../conf/distro/include/poky-default-revisions.inc |    6 +++---
>   .../kern-tools/kern-tools-native_git.bb            |    2 +-
>   3 files changed, 6 insertions(+), 6 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Oops, both where pulled

Sau!



  parent reply	other threads:[~2011-01-28  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 21:46 [PATCH 0/2] linux-yocto: consolidated pull request Bruce Ashfield
2011-01-24 21:46 ` [PATCH 1/2] linux-yocto: allow multiple BSPs per branch Bruce Ashfield
2011-01-24 21:46 ` [PATCH 2/2] linux-yocto: update SRCREVs for emenlow Bruce Ashfield
2011-01-28  1:29   ` Saul Wold
2011-01-28  1:29     ` [poky] " Saul Wold
2011-01-28  1:29 ` Saul Wold [this message]
2011-01-28  1:29   ` [poky] [PATCH 0/2] linux-yocto: consolidated pull request Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2011-02-01 17:25 Bruce Ashfield
2015-09-18 19:21 Bruce Ashfield
2016-01-27  4:27 [PATCH 0/2]: " Bruce Ashfield

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=4D421C16.2070308@intel.com \
    --to=saul.wold@intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.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.