From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Xu Yang <xu.yang_2@nxp.com>, Andi Kleen <ak@linux.intel.com>,
Zixian Cai <fzczx123@gmail.com>, Paran Lee <p4ranlee@gmail.com>,
Ben Gainey <ben.gainey@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Python module cleanup
Date: Thu, 19 Sep 2024 00:54:16 +0200 [thread overview]
Message-ID: <20240918225418.166717-1-irogers@google.com> (raw)
Remove workarounds for Python 2 module support. Constify variables and
parameters to functions.
Ian Rogers (2):
perf python: Remove python 2 scripting support
perf python: Constify variables and parameters
.../scripts/python/Perf-Trace-Util/Context.c | 18 ---
tools/perf/util/python.c | 128 ++++++------------
.../scripting-engines/trace-event-python.c | 63 +--------
3 files changed, 44 insertions(+), 165 deletions(-)
--
2.46.0.662.g92d0881bb0-goog
next reply other threads:[~2024-09-18 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 22:54 Ian Rogers [this message]
2024-09-18 22:54 ` [PATCH v1 1/2] perf python: Remove python 2 scripting support Ian Rogers
2024-09-19 1:29 ` Andi Kleen
2024-09-19 4:45 ` Ian Rogers
2024-09-30 21:26 ` Namhyung Kim
2024-10-01 11:22 ` Andi Kleen
2024-10-01 12:49 ` James Clark
2024-10-01 13:47 ` Ian Rogers
2024-10-10 1:26 ` Namhyung Kim
2024-10-01 12:52 ` James Clark
2024-09-18 22:54 ` [PATCH v1 2/2] perf python: Constify variables and parameters Ian Rogers
2024-10-01 12:52 ` James Clark
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=20240918225418.166717-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.gainey@arm.com \
--cc=fzczx123@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=p4ranlee@gmail.com \
--cc=peterz@infradead.org \
--cc=xu.yang_2@nxp.com \
/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
all inboxes | Powered by JetHome®