From: tom.zanussi@intel.com
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Subject: [PATCH 0/3] perf-scripting/perf-tui features, v2
Date: Fri, 6 Jul 2012 15:29:56 -0500 [thread overview]
Message-ID: <cover.1341606068.git.tom.zanussi@intel.com> (raw)
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.
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
next reply other threads:[~2012-07-06 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 20:29 tom.zanussi [this message]
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
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=cover.1341606068.git.tom.zanussi@intel.com \
--to=tom.zanussi@intel.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