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: update 3.4 SRCREVs (perf + unionfs fix)
Date: Mon, 09 Jul 2012 09:30:43 -0700 [thread overview]
Message-ID: <4FFB0733.1050902@linux.intel.com> (raw)
In-Reply-To: <cover.1341845577.git.bruce.ashfield@windriver.com>
On 07/09/2012 07:59 AM, Bruce Ashfield wrote:
> Saul/Richard,
>
> I was waiting on the resend of Tom's perf series to send the updated
> kernel parts for this. That's out, and the kernel parts now need to
> be updated.
>
> I've also staged a unionfs build fix along with the perf updates.
>
> Cheers,
>
> Bruce
>
> cc: Tom Zanussi <tom.zanussi@intel.com>
>
> The following changes since commit f40ce3e1f4ceebc90b3c058dc82750829149c21d:
>
> package_rpm: Avoid duplicate package generation failures (2012-07-09 11:38:02 +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 (1):
> linux-yocto/3.4: perf scripting & unionfs fixes
>
> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 6 +++---
> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 14 +++++++-------
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2012-07-09 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:59 [PATCH 0/1] linux-yocto: update 3.4 SRCREVs (perf + unionfs fix) Bruce Ashfield
2012-07-09 14:59 ` [PATCH 1/1] linux-yocto/3.4: perf scripting & unionfs fixes Bruce Ashfield
2012-07-09 16:30 ` Saul Wold [this message]
2012-07-09 17:08 ` [PATCH 0/1] linux-yocto: update 3.4 SRCREVs (perf + unionfs fix) Tom Zanussi
2012-07-09 17:20 ` 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=4FFB0733.1050902@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