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>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Add a runs-per-test flag
Date: Tue, 7 Jan 2025 14:01:49 -0800 [thread overview]
Message-ID: <20250107220152.1213959-1-irogers@google.com> (raw)
In the v1 patch Kan and I noted cleanup that would make the code
cleaner and less indented:
https://lore.kernel.org/lkml/20241109160219.49976-1-irogers@google.com/
Add patches doing some builtin-test.c cleanup and then add the
runs-per-test flag.
Ian Rogers (3):
perf test: Rename functions and variables for better clarity
perf test: Send list output to stdout rather than stderr
perf test: Add a runs-per-test flag
tools/perf/tests/builtin-test.c | 223 +++++++++++++++-----------------
1 file changed, 107 insertions(+), 116 deletions(-)
--
2.47.1.613.gc27f4b7a9f-goog
next reply other threads:[~2025-01-07 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 22:01 Ian Rogers [this message]
2025-01-07 22:01 ` [PATCH v2 1/3] perf test: Rename functions and variables for better clarity Ian Rogers
2025-01-07 22:01 ` [PATCH v2 2/3] perf test: Send list output to stdout rather than stderr Ian Rogers
2025-01-07 22:01 ` [PATCH v2 3/3] perf test: Add a runs-per-test flag Ian Rogers
2025-01-08 19:09 ` Namhyung Kim
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=20250107220152.1213959-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@linaro.org \
--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=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