Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] linux-yocto/3.2: perf scripting changes
Date: Tue, 10 Jul 2012 11:07:37 -0700	[thread overview]
Message-ID: <4FFC6F69.8080508@linux.intel.com> (raw)
In-Reply-To: <cover.1341854902.git.bruce.ashfield@windriver.com>

On 07/09/2012 10:31 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> I had meant to send these along with the 3.4 update, and managed to get
> distracted and miss them.
>
> These are the SRCREV updates for the 3.2 kernel to support TomZ's recent
> perf scripting work.
>
> Cheers,
>
> Bruce
>
> cc: Tom Zanussi <tom.zanussi@intel.com>
>
> The following changes since commit 90ad663909c0c8a405b22a510c9f957007d02669:
>
>    upstream_tracking: update boost (2012-07-09 17:21:38 +0100)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib zedd/kernel-oe
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
>    linux-yocto/3.2: perf scripting updates
>
>   meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb   |    6 +++---
>   meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb |    4 ++--
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb      |   14 +++++++-------
>   3 files changed, 12 insertions(+), 12 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-07-10 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 17:31 [PATCH 0/1] linux-yocto/3.2: perf scripting changes Bruce Ashfield
2012-07-09 17:31 ` [PATCH 1/1] linux-yocto/3.2: perf scripting updates Bruce Ashfield
2012-07-10 18:07 ` Saul Wold [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=4FFC6F69.8080508@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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