From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jeremy Cline <jeremy@jcline.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
"Herton R . Krzesinski" <herton@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Improve Python 3 support in perf
Date: Thu, 28 Jun 2018 11:44:31 -0300 [thread overview]
Message-ID: <20180628144431.GA20184@kernel.org> (raw)
In-Reply-To: <0100016341a7217a-d48a8d8a-c7ed-4857-82ef-9e2e599364e2-000000@email.amazonses.com>
Em Tue, May 08, 2018 at 09:27:42PM +0000, Jeremy Cline escreveu:
> Hi folks,
>
> This patch set adds Python 3 support to a number of perf scripts,
> including those generated by "perf script -g python", without breaking
> Python 2 compatibility.
Argh, this fell thru the cracks, sorry, all seems ok, applied,
- Arnaldo
> Jeremy Cline (8):
> perf tools: Generate a Python script compatible with Python 2 and 3
> perf scripts python: Add Python 3 support to Core.py
> perf scripts python: Add Python 3 support to SchedGui.py
> perf scripts python: Add Python 3 support to Util.py
> perf scripts python: Add Python 3 support to EventClass.py
> perf scripts python: Add Python 3 support to sched-migration.py
> perf scripts python: Add Python 3 support to stat-cpi.py
> perf tests: Add Python 3 support to attr.py
>
> .../Perf-Trace-Util/lib/Perf/Trace/Core.py | 40 ++++++++-----------
> .../lib/Perf/Trace/EventClass.py | 4 +-
> .../lib/Perf/Trace/SchedGui.py | 2 +-
> .../Perf-Trace-Util/lib/Perf/Trace/Util.py | 11 ++---
> tools/perf/scripts/python/sched-migration.py | 14 ++++---
> tools/perf/scripts/python/stat-cpi.py | 5 ++-
> tools/perf/tests/attr.py | 32 +++++++++------
> .../scripting-engines/trace-event-python.c | 29 +++++++-------
> 8 files changed, 74 insertions(+), 63 deletions(-)
>
> --
> 2.17.0
prev parent reply other threads:[~2018-06-28 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 21:27 [PATCH 0/8] Improve Python 3 support in perf Jeremy Cline
2018-06-28 14:44 ` Arnaldo Carvalho de Melo [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=20180628144431.GA20184@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=herton@redhat.com \
--cc=jeremy@jcline.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).