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
Subject: [PATCH 0/2] linux-yocto/kern-tools (v2)
Date: Thu, 22 Nov 2012 12:48:27 -0500	[thread overview]
Message-ID: <cover.1353606229.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

Here's a quick update for some configuration changes that came
in for the x86 BSPs. I've merged and tested them, so there's no
sense sitting on the change.

I also noticed that in my rushing, I sent my update for the
kern-tools without pushing the change to the master repository,
forcing Richard to undo the change .. sorry about that, I assure
you that the revision is really in place this time.

Cheers,

Bruce

The following changes since commit 14f7c9c9d87e1a9b0c20d78d528068fd9f1a27cf:

  Revert "kern-tools: report missing config fragments by name" (2012-11-22 08:59:24 +0000)

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 (2):
  linux-yocto-3.4: gcc optimization config feature
  kern-tools: report missing config fragments by name

 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb |    2 +-
 meta/recipes-kernel/linux/linux-yocto_3.4.bb            |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
1.7.10.4




             reply	other threads:[~2012-11-22 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 17:48 Bruce Ashfield [this message]
2012-11-22 17:48 ` [PATCH 1/2] linux-yocto-3.4: gcc optimization config feature Bruce Ashfield
2012-11-22 17:48 ` [PATCH 2/2] kern-tools: report missing config fragments by name 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.1353606229.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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