Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/2] linux-yocto: streamlined repository support + fixes
Date: Tue,  8 May 2012 10:47:35 -0400	[thread overview]
Message-ID: <cover.1336487836.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

This pull requests represents some changes that I've been running here
for the past 1.5 months. It is a re-working of the tools and recipes to
allow more repository types to support the kern tools (branching and
fragments). 

It's one largish patch that consolidates recipe updates, tool changes
and streamlining of the patching phase.

This is step one, there are several more to follow after this merges
into the tree. Namely:
  
  - updated documents on what an inheriting recipe needs to do
  - movement of the linux-yocto-custom recipe from meta-kernel-dev
    to somewhere more visible
  - updates to meta-kernel-dev to fix those recipes
  - removal of the 2.6.37 recipe and introduction of the 3.4 kernel
    recipe
  - additional streamlining of the tools (more code deleted!).

I've converted the linux-yocto* recipes (except for 2.6.37, since I'll be
removing it shortly) and have built 3.0, 3.2 and -dev kernels for all the
boards I can. It's ready to go, but can also use a run through a 
nightly build before it merged (the changes were a bit tricky with a lot
of existing use cases to ensure were not broken).

FYI: I stacked this on top of my last pull request, let me know if this
needs to be rebased.

Cheers,

Bruce

The following changes since commit e116928e3a1af803b9c6fa06236902ad730f7bf8:

  linux-yocto/3.0: mm/msync: tweak tmpfs patch for syscall msync (2012-05-08 10:18:56 -0400)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel-dev
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-dev

Bruce Ashfield (2):
  linux-yocto: streamline support for multiple upstream repo types
  kern-tools: integrate minor fixes

 meta/classes/kernel-yocto.bbclass                  |  115 ++++++++++----------
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb    |    1 +
 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb    |    2 +
 meta/recipes-kernel/linux/linux-yocto.inc          |    7 +-
 meta/recipes-kernel/linux/linux-yocto_2.6.37.bb    |    2 +
 meta/recipes-kernel/linux/linux-yocto_3.0.bb       |   23 +++--
 meta/recipes-kernel/linux/linux-yocto_3.2.bb       |    2 +
 8 files changed, 86 insertions(+), 68 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-05-08 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 14:47 Bruce Ashfield [this message]
2012-05-08 14:47 ` [PATCH 1/2] linux-yocto: streamline support for multiple upstream repo types Bruce Ashfield
2012-05-08 14:47 ` [PATCH 2/2] kern-tools: integrate minor fixes Bruce Ashfield
2012-05-08 15:18 ` [PATCH 0/2] linux-yocto: streamlined repository support + fixes Richard Purdie

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.1336487836.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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