From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: eranian@google.com, Ian Rogers <irogers@google.com>
Subject: [PATCH 0/3] Some exit code tidying
Date: Wed, 28 Jul 2021 23:24:48 -0700 [thread overview]
Message-ID: <20210729062451.1349566-1-irogers@google.com> (raw)
I'm interested in varying error codes for things like parse event
failures. This is some cleanup to use more intention revealing names
in the existing exit/test cases.
Ian Rogers (3):
libperf: Prefer exit(EXIT_SUCCESS) over exit(0)
tools perf: Prefer exit(EXIT_*) over exit(0|1)
perf test: Be more consistent in use of TEST_*
tools/lib/perf/tests/test-evlist.c | 2 +-
tools/perf/arch/x86/tests/bp-modify.c | 4 +-
tools/perf/arch/x86/tests/rdpmc.c | 8 +-
tools/perf/bench/inject-buildid.c | 8 +-
tools/perf/bench/numa.c | 2 +-
tools/perf/bench/sched-messaging.c | 6 +-
tools/perf/bench/sched-pipe.c | 4 +-
tools/perf/bench/syscall.c | 2 +-
tools/perf/builtin-c2c.c | 2 +-
tools/perf/builtin-ftrace.c | 2 +-
tools/perf/builtin-mem.c | 2 +-
tools/perf/builtin-script.c | 4 +-
tools/perf/perf.c | 8 +-
tools/perf/tests/attr.c | 2 +-
tools/perf/tests/bitmap.c | 2 +-
tools/perf/tests/bp_account.c | 4 +-
tools/perf/tests/bp_signal.c | 51 +++++++--
tools/perf/tests/code-reading.c | 12 +-
tools/perf/tests/cpumap.c | 10 +-
tools/perf/tests/dso-data.c | 8 +-
tools/perf/tests/dwarf-unwind.c | 14 ++-
tools/perf/tests/event-times.c | 2 +-
tools/perf/tests/evsel-roundtrip-name.c | 14 +--
tools/perf/tests/evsel-tp-sched.c | 28 ++---
tools/perf/tests/expr.c | 4 +-
tools/perf/tests/fdarray.c | 4 +-
tools/perf/tests/genelf.c | 2 +-
tools/perf/tests/hists_cumulate.c | 2 +-
tools/perf/tests/hists_filter.c | 12 +-
tools/perf/tests/hists_link.c | 33 +++---
tools/perf/tests/keep-tracking.c | 4 +-
tools/perf/tests/kmod-path.c | 6 +-
tools/perf/tests/mem.c | 4 +-
tools/perf/tests/mem2node.c | 2 +-
tools/perf/tests/mmap-basic.c | 10 +-
tools/perf/tests/mmap-thread-lookup.c | 2 +-
tools/perf/tests/openat-syscall-all-cpus.c | 4 +-
tools/perf/tests/openat-syscall-tp-fields.c | 4 +-
tools/perf/tests/openat-syscall.c | 6 +-
tools/perf/tests/parse-events.c | 118 ++++++++++----------
tools/perf/tests/parse-metric.c | 16 +--
tools/perf/tests/parse-no-sample-id-all.c | 4 +-
tools/perf/tests/perf-hooks.c | 2 +-
tools/perf/tests/perf-record.c | 2 +-
tools/perf/tests/perf-time-to-tsc.c | 4 +-
tools/perf/tests/pfm.c | 4 +-
tools/perf/tests/pmu-events.c | 36 +++---
tools/perf/tests/pmu.c | 16 +--
tools/perf/tests/python-use.c | 2 +-
tools/perf/tests/sample-parsing.c | 10 +-
tools/perf/tests/stat.c | 12 +-
tools/perf/tests/sw-clock.c | 8 +-
tools/perf/tests/switch-tracking.c | 9 +-
tools/perf/tests/task-exit.c | 12 +-
tools/perf/tests/tests.h | 4 +-
tools/perf/tests/thread-map.c | 8 +-
tools/perf/tests/thread-maps-share.c | 2 +-
tools/perf/tests/time-utils-test.c | 2 +-
tools/perf/tests/topology.c | 2 +-
tools/perf/tests/vmlinux-kallsyms.c | 6 +-
tools/perf/tests/wp.c | 10 +-
tools/perf/ui/tui/setup.c | 4 +-
tools/perf/util/dlfilter.c | 2 +-
tools/perf/util/help-unknown-cmd.c | 2 +-
64 files changed, 319 insertions(+), 278 deletions(-)
--
2.32.0.432.gabb21c7263-goog
next reply other threads:[~2021-07-29 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 6:24 Ian Rogers [this message]
2021-07-29 6:24 ` [PATCH 1/3] libperf: Prefer exit(EXIT_SUCCESS) over exit(0) Ian Rogers
2021-07-29 6:24 ` [PATCH 2/3] tools perf: Prefer exit(EXIT_*) over exit(0|1) Ian Rogers
2021-07-29 6:24 ` [PATCH 3/3] perf test: Be more consistent in use of TEST_* Ian Rogers
2021-07-29 13:39 ` Riccardo Mancini
2021-07-29 18:24 ` Ian Rogers
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=20210729062451.1349566-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.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;
as well as URLs for NNTP newsgroup(s).