From: tip-bot for Namhyung Kim <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: jolsa@kernel.org, hpa@zytor.com, acme@redhat.com,
namhyung@kernel.org, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org, mingo@kernel.org,
tglx@linutronix.de
Subject: [tip:perf/urgent] perf record: Honor --quiet option properly
Date: Tue, 21 Feb 2017 00:18:19 -0800 [thread overview]
Message-ID: <tip-68ba32352d51474d163d58e084b62a12bb610b21@git.kernel.org> (raw)
In-Reply-To: <20170217081742.17417-7-namhyung@kernel.org>
Commit-ID: 68ba32352d51474d163d58e084b62a12bb610b21
Gitweb: http://git.kernel.org/tip/68ba32352d51474d163d58e084b62a12bb610b21
Author: Namhyung Kim <namhyung@kernel.org>
AuthorDate: Fri, 17 Feb 2017 17:17:42 +0900
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Mon, 20 Feb 2017 11:50:36 -0300
perf record: Honor --quiet option properly
It should call perf_quiet_option() to suppress messages.
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: kernel-team@lge.com
Link: http://lkml.kernel.org/r/20170217081742.17417-7-namhyung@kernel.org
[ Fix merge clash with 483635a9d080 ("perf record: Add -a as default target") ]
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/builtin-record.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index 451b11e..bc84a37 100644
--- a/tools/perf/builtin-record.c
+++ b/tools/perf/builtin-record.c
@@ -1677,6 +1677,8 @@ int cmd_record(int argc, const char **argv, const char *prefix __maybe_unused)
argc = parse_options(argc, argv, record_options, record_usage,
PARSE_OPT_STOP_AT_NON_OPTION);
+ if (quiet)
+ perf_quiet_option();
/* Make system wide (-a) the default target. */
if (!argc && target__none(&rec->opts.target))
prev parent reply other threads:[~2017-02-21 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 8:17 [PATCHSET 0/6] perf tools: Add -q/--quiet option to suppress messages (v1) Namhyung Kim
2017-02-17 8:17 ` [PATCH 1/6] perf utils: Add perf_quiet_option() Namhyung Kim
2017-02-21 8:15 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2017-02-17 8:17 ` [PATCH 2/6] perf utils: Check verbose flag properly Namhyung Kim
2017-02-20 14:35 ` Arnaldo Carvalho de Melo
2017-02-21 1:38 ` Namhyung Kim
2017-02-21 8:16 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2017-02-17 8:17 ` [PATCH 3/6] perf report: Add -q/--quiet option Namhyung Kim
2017-02-17 11:09 ` Jiri Olsa
2017-02-19 0:21 ` Namhyung Kim
2017-02-20 19:08 ` Arnaldo Carvalho de Melo
2017-02-21 1:40 ` Namhyung Kim
2017-02-21 8:16 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2017-02-17 8:17 ` [PATCH 4/6] perf diff: " Namhyung Kim
2017-02-21 8:17 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2017-02-17 8:17 ` [PATCH 5/6] perf annotate: " Namhyung Kim
2017-02-21 8:17 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2017-02-17 8:17 ` [PATCH 6/6] perf record: Honor quiet option properly Namhyung Kim
2017-02-21 8:18 ` tip-bot for Namhyung Kim [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=tip-68ba32352d51474d163d58e084b62a12bb610b21@git.kernel.org \
--to=tipbot@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
/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).