From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <tom.zanussi@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 0/4] linux-yocto-3.2/standard/base: perf scripting updates
Date: Tue, 3 Jul 2012 15:08:18 -0400 [thread overview]
Message-ID: <4FF34322.90004@windriver.com> (raw)
In-Reply-To: <cover.1341337418.git.tom.zanussi@intel.com>
On 12-07-03 02:09 PM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi<tom.zanussi@intel.com>
>
> This patchset comprises the kernel side of the modifications needed to
> enable the Perl and Python bindings for perf scripting.
>
> Please pull into linux-yocto-3.2 standard/base.
Ack'd. Same as the 3.4 variant. Queued pending any review comments.
Cheers,
Bruce
>
> Thanks,
>
> Tom
>
> The following changes are available in the git repository at:
>
> git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/3.2-perf-scripting-standard-base
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.2-perf-scripting-standard-base
>
> Tom Zanussi (4):
> Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
> perf: use pkg-config instead of python-config
> perf: add 'libperl not found' warning
> perf: change --root to --prefix for python install
>
> tools/perf/Makefile | 90 +++++++++++++++++++++++++++++++++++++++++++++++++--
> 1 files changed, 87 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2012-07-03 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 18:09 [PATCH 0/4] linux-yocto-3.2/standard/base: perf scripting updates tom.zanussi
2012-07-03 18:09 ` [PATCH 1/4] Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON" tom.zanussi
2012-07-03 18:09 ` [PATCH 2/4] perf: use pkg-config instead of python-config tom.zanussi
2012-07-03 18:09 ` [PATCH 3/4] perf: add 'libperl not found' warning tom.zanussi
2012-07-03 18:09 ` [PATCH 4/4] perf: change --root to --prefix for python install tom.zanussi
2012-07-03 19:08 ` Bruce Ashfield [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=4FF34322.90004@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.