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/3] perf-scripting/perf-tui features, v2
Date: Mon, 09 Jul 2012 00:55:24 -0700 [thread overview]
Message-ID: <4FFA8E6C.90504@linux.intel.com> (raw)
In-Reply-To: <1341724701.6761.177.camel@trz-ThinkPad-T420>
On 07/07/2012 10:18 PM, Tom Zanussi wrote:
> On Fri, 2012-07-06 at 15:29 -0500, tom.zanussi@intel.com wrote:
>> From: Tom Zanussi <tom.zanussi@intel.com>
>>
>> This patchset adds perf-scriping and perf-tui features as
>> a per-arch thing rather than per-machine, as suggested by
>> Richard Purdie.
>>
>> I just started testing this, it works so far, but thought
>> I'd put it out there now in case there were comments before
>> putting too much effort into that, and possibly giving other
>> people a chance to try it out.
>>
>
> Looks fine after more build-testing: qemux86, qemux86-64, crownbay,
> sugarbay, qemuarm and qemuppc both with and without perf-scripting and
> perf-tui, and builds without perf as well all build fine here.
>
Tom, I am sorry, I am not sure how else to say this, I have tested
master with the only the following change and I am still getting the
the setup.py failure mentioned.
I am not sure what else to suspect at this point, this is Master plus 3
commits, please help me understand where I have gone wrong.
This is the branch I have tested, which is 3 commits pasted Master:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgw/fail
Thanks
Sau!
> Tom
>
>> The following changes since commit 5051e9837fa698e03d0a7a8a918ee7aa98409ce1:
>> Robert P. J. Day (1):
>> bitbake: usermanual: Fix missing markup
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib.git tzanussi/perf-scripting-v2
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/perf-scripting-v2
>>
>> Tom Zanussi (3):
>> perf: add perf.inc
>> perf: add arch-specific perf-scripting feature
>> perf: add arch-specific perf-tui feature
>>
>> meta/recipes-kernel/perf/perf.inc | 30 ++++++++++++++++++++++++++++++
>> meta/recipes-kernel/perf/perf_3.4.bb | 18 +++++++++++++++---
>> 2 files changed, 45 insertions(+), 3 deletions(-)
>> create mode 100644 meta/recipes-kernel/perf/perf.inc
>>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-07-09 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 20:29 [PATCH 0/3] perf-scripting/perf-tui features, v2 tom.zanussi
2012-07-06 20:29 ` [PATCH 1/3] perf: add perf.inc tom.zanussi
2012-07-06 20:29 ` [PATCH 2/3] perf: add arch-specific perf-scripting feature tom.zanussi
2012-07-08 22:00 ` Saul Wold
2012-07-09 4:02 ` Tom Zanussi
2012-07-06 20:29 ` [PATCH 3/3] perf: add arch-specific perf-tui feature tom.zanussi
2012-07-08 5:18 ` [PATCH 0/3] perf-scripting/perf-tui features, v2 Tom Zanussi
2012-07-09 7:55 ` Saul Wold [this message]
2012-07-09 13:47 ` Tom Zanussi
2012-07-09 13:51 ` 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=4FFA8E6C.90504@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