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/6] linux-yocto/kern-tools: consolidated pull request
Date: Tue,  4 Sep 2012 08:40:31 -0400	[thread overview]
Message-ID: <cover.1346762109.git.bruce.ashfield@windriver.com> (raw)

Saul/Richard,

This is largely the same pull request that I sent a week ago, and
I've had things fixed for a bit, but I didn't want to send it 
again during my travel .. and then a long weekend.

So here's the request again. 

It is a content update to 3.4.9 + some tool tweaking for problems 
found by Khem, Matthew Foster and Tom Zanussi. With the tools fixes,
we have all known use cases back up and working.

The content update has been tested for 2 weeks now and is safe,
we do know that the -rt kernel has some issues at the moment, and
once this pull request is sent, I'll do a refresh on -rt and get
that problem fixed.

Cheers,

Bruce

The following changes since commit bb86a22ba6f90902644c11f984ae4c171ba36624:

  yocto-docs/.gitignore: Final fix to ignore mega-manual. (2012-09-04 12:55:03 +0100)

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 (6):
  kern-tools: fix forced branching
  linux-yocto: fix unapplied patch error message
  linux-yocto: check for bad SRCREV before branch checks
  kern-tools: fix non-inheriting branch names
  linux-yocto/3.4: v3.4.9, unionfs, perf and configuration changes
  linux-yocto/3.2/3.4: arm: Fix linking errors with binutils 2.23

 meta/classes/kernel-yocto.bbclass                  |   18 ++++++++++--------
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb    |    4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb    |    8 ++++----
 meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb  |    2 +-
 meta/recipes-kernel/linux/linux-yocto_3.2.bb       |   12 ++++++------
 meta/recipes-kernel/linux/linux-yocto_3.4.bb       |   16 ++++++++--------
 7 files changed, 32 insertions(+), 30 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-09-04 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 12:40 Bruce Ashfield [this message]
2012-09-04 12:40 ` [PATCH 1/6] kern-tools: fix forced branching Bruce Ashfield
2012-09-04 12:40 ` [PATCH 2/6] linux-yocto: fix unapplied patch error message Bruce Ashfield
2012-09-04 12:40 ` [PATCH 3/6] linux-yocto: check for bad SRCREV before branch checks Bruce Ashfield
2012-09-04 12:40 ` [PATCH 4/6] kern-tools: fix non-inheriting branch names Bruce Ashfield
2012-09-04 12:40 ` [PATCH 5/6] linux-yocto/3.4: v3.4.9, unionfs, perf and configuration changes Bruce Ashfield
2012-09-04 12:40 ` [PATCH 6/6] linux-yocto/3.2/3.4: arm: Fix linking errors with binutils 2.23 Bruce Ashfield
2012-09-04 13:47 ` [PATCH 0/6] linux-yocto/kern-tools: consolidated pull request 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.1346762109.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