Poky Project Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com,
	openembedded-core@lists.openembedded.org, poky@yoctoproject.org,
	saul.wold@intel.com
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Mon,  9 May 2011 14:34:03 -0400	[thread overview]
Message-ID: <cover.1304965560.git.bruce.ashfield@windriver.com> (raw)

Saul/Richard,

The first two patches are a split and resend of the machine
movement patch:

[
   linux-yocto: move non-core machines to meta-yocto

   The machine configuration of the non-core (non-qemu) machines
   has moved to meta-yocto. Moving the branch mappings, compatibility
   and SRCREVs of these machines to meta-yocto should also be
   done.

  Anyone using meta-yocto to build these machines will see no impact
  from this change.
]

Patch #3 is a sanity check that shows a problem that Tom managed
to hit, and cause us some significant debug time. If for some 
reason (we still don't have a root cause) the kernel repo is cloned
without tags and/or meta data, we can now detect it and throw an
informative error message rather than generating meta data and
building "something".

cc: Darren Hart <dvhart@linux.intel.com> 
cc: Tom Zanussi <tom.zanussi@intel.com>

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 (3):
  linux-yocto: remove non-core (qemu) machine compatibility
  linux-yocto: move non-core machines to meta-yocto
  linux-yocto: error if meta data not present

 meta-yocto/conf/layer.conf                         |    3 ++-
 .../linux/linux-yocto-stable_git.bbappend          |   12 ++++++++++++
 .../recipes-kernel/linux/linux-yocto_git.bbappend  |   12 ++++++++++++
 meta/classes/kernel-yocto.bbclass                  |    5 ++++-
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 .../recipes-kernel/linux/linux-yocto-stable_git.bb |   10 +---------
 meta/recipes-kernel/linux/linux-yocto_git.bb       |   15 ++++-----------
 7 files changed, 36 insertions(+), 23 deletions(-)
 create mode 100644 meta-yocto/recipes-kernel/linux/linux-yocto-stable_git.bbappend
 create mode 100644 meta-yocto/recipes-kernel/linux/linux-yocto_git.bbappend



             reply	other threads:[~2011-05-09 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 18:34 Bruce Ashfield [this message]
2011-05-09 18:34 ` [PATCH 1/3] linux-yocto: remove non-core (qemu) machine compatibility Bruce Ashfield
2011-05-09 18:34 ` [PATCH 2/3] linux-yocto: move non-core machines to meta-yocto Bruce Ashfield
2011-05-09 18:34 ` [PATCH 3/3] linux-yocto: error if meta data not present Bruce Ashfield
2011-05-10 17:53 ` [OE-core] [PATCH 0/3] linux-yocto: consolidated pull request Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2011-05-05  4:53 Bruce Ashfield
2011-01-17 21:57 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=cover.1304965560.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox