All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/2] meta-intel: improve interactions with common layer
Date: Sat, 25 Feb 2012 10:28:36 -0600	[thread overview]
Message-ID: <1330187316.2485.242.camel@elmorro> (raw)
In-Reply-To: <cover.1330076070.git.paul.eggleton@linux.intel.com>

On Fri, 2012-02-24 at 09:38 +0000, Paul Eggleton wrote:
> At the moment it is possible to enable one of the sub-layers of
> meta-intel (e.g. meta-n450) without also enabling the meta-intel common
> layer, which can lead to some nasty parsing errors. Here are two patches
> to handle this situation in a nicer way.
> 
> (Note that BitBake currently does not actually terminate when
> LAYERDEPENDS are not satisfied - I've got a patch queued to fix this.)
> 
> The following changes since commit 1ca68394faf33416f2aabee27323da7510ad6609:
> 
>   netbase: put sys940x specific interfaces file in MACHINE directory (2012-02-10 17:27:27 -0800)
> 
> are available in the git repository at:
>   git://git.yoctoproject.org/meta-intel-contrib paule/layerdepends
>   http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=paule/layerdepends
> 

Pulled into meta-intel/master.  Thanks, Paul!

Tom

> Paul Eggleton (2):
>   meta-intel: replace "include" with "require"
>   meta-intel: add LAYERDEPENDS for layers needing the meta-intel common
>     layer
> 
>  meta-cedartrail/conf/layer.conf                 |    2 ++
>  meta-cedartrail/conf/machine/cedartrail.conf    |    2 +-
>  meta-crownbay/conf/layer.conf                   |    2 ++
>  meta-crownbay/conf/machine/crownbay-noemgd.conf |    4 ++--
>  meta-crownbay/conf/machine/crownbay.conf        |    4 ++--
>  meta-emenlow/conf/layer.conf                    |    2 ++
>  meta-emenlow/conf/machine/emenlow.conf          |    4 ++--
>  meta-fishriver/conf/layer.conf                  |    2 ++
>  meta-fishriver/conf/machine/fishriver.conf      |    2 +-
>  meta-fri2/conf/layer.conf                       |    2 ++
>  meta-fri2/conf/machine/fri2-noemgd.conf         |    4 ++--
>  meta-fri2/conf/machine/fri2.conf                |    4 ++--
>  meta-jasperforest/conf/layer.conf               |    2 ++
>  meta-n450/conf/layer.conf                       |    2 ++
>  meta-n450/conf/machine/n450.conf                |    4 ++--
>  meta-romley/conf/layer.conf                     |    2 ++
>  meta-romley/conf/machine/romley.conf            |    2 +-
>  meta-sugarbay/conf/layer.conf                   |    2 ++
>  meta-sys940x/conf/layer.conf                    |    2 ++
>  meta-sys940x/conf/machine/sys940x-noemgd.conf   |    4 ++--
>  meta-sys940x/conf/machine/sys940x.conf          |    4 ++--
>  21 files changed, 39 insertions(+), 19 deletions(-)
> 




      parent reply	other threads:[~2012-02-25 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  9:38 [PATCH 0/2] meta-intel: improve interactions with common layer Paul Eggleton
2012-02-24  9:38 ` [PATCH 1/2] meta-intel: replace "include" with "require" Paul Eggleton
2012-02-24  9:38 ` [PATCH 2/2] meta-intel: add LAYERDEPENDS for layers needing the meta-intel common layer Paul Eggleton
2012-02-25 16:28 ` Tom Zanussi [this message]

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=1330187316.2485.242.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --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.