From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: linux-perf-users@vger.kernel.org, namhyung@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v2 0/2] perf: Fix "kernel lock contention analysis" test by not printing warnings in quiet mode
Date: Wed, 26 Oct 2022 11:36:22 -0300 [thread overview]
Message-ID: <Y1lF5lZ26nTBpyaR@kernel.org> (raw)
In-Reply-To: <20221018094137.783081-1-james.clark@arm.com>
Em Tue, Oct 18, 2022 at 10:41:34AM +0100, James Clark escreveu:
> This is V2, but the previous patch was titled 'perf: Fix "Track with
> sched_switch" test by not printing warnings in quiet mode'
>
> Changes since V1:
>
> * Add a commit to make the behavior consistent between tools and
> update the docs
> * Fix the incorrect test name in the commit message
Thanks, applied.
- Arnaldo
> James Clark (2):
> perf: Fix "kernel lock contention analysis" test by not printing
> warnings in quiet mode
> perf: Make quiet mode consistent between tools
>
> tools/perf/Documentation/perf-annotate.txt | 2 +-
> tools/perf/Documentation/perf-diff.txt | 2 +-
> tools/perf/Documentation/perf-lock.txt | 2 +-
> tools/perf/Documentation/perf-probe.txt | 2 +-
> tools/perf/Documentation/perf-record.txt | 2 +-
> tools/perf/Documentation/perf-report.txt | 2 +-
> tools/perf/Documentation/perf-stat.txt | 4 ++--
> tools/perf/bench/numa.c | 9 +++++----
> tools/perf/builtin-annotate.c | 2 +-
> tools/perf/builtin-diff.c | 2 +-
> tools/perf/builtin-lock.c | 2 +-
> tools/perf/builtin-probe.c | 7 +++----
> tools/perf/builtin-record.c | 2 +-
> tools/perf/builtin-report.c | 2 +-
> tools/perf/builtin-stat.c | 8 ++++----
> tools/perf/ui/util.c | 5 +++++
> tools/perf/util/stat.h | 1 -
> 17 files changed, 30 insertions(+), 26 deletions(-)
>
> --
> 2.28.0
--
- Arnaldo
prev parent reply other threads:[~2022-10-26 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 9:41 [PATCH v2 0/2] perf: Fix "kernel lock contention analysis" test by not printing warnings in quiet mode James Clark
2022-10-18 9:41 ` [PATCH v2 1/2] " James Clark
2022-10-18 9:41 ` [PATCH v2 2/2] perf: Make quiet mode consistent between tools James Clark
2022-10-18 19:20 ` [PATCH v2 0/2] perf: Fix "kernel lock contention analysis" test by not printing warnings in quiet mode Arnaldo Carvalho de Melo
2022-10-26 14:36 ` 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=Y1lF5lZ26nTBpyaR@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--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).