linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yisheng Xie <xieyisheng1@huawei.com>
To: <acme@redhat.com>
Cc: <mingo@redhat.com>, <peterz@infradead.org>, <namhyung@kernel.org>,
	<jolsa@redhat.com>, <alexander.shishkin@linux.intel.com>,
	<linux-kernel@vger.kernel.org>, <kan.liang@linux.intel.com>,
	Yisheng Xie <xieyisheng1@huawei.com>
Subject: [PATCH v2 -perf/core 2/2] perf debug: Avoid set quiet once more
Date: Tue, 13 Mar 2018 20:31:14 +0800	[thread overview]
Message-ID: <1520944274-37001-2-git-send-email-xieyisheng1@huawei.com> (raw)
In-Reply-To: <1520944274-37001-1-git-send-email-xieyisheng1@huawei.com>

When use --quiet to disable log, we will set quiet first, then check the
quiet to decide whether need to call perf_quiet_option, so no need to set
the quiet once more.

Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
---
 - This is a new add-on patch

 tools/perf/util/debug.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/tools/perf/util/debug.c b/tools/perf/util/debug.c
index f3a71db..3d64596 100644
--- a/tools/perf/util/debug.c
+++ b/tools/perf/util/debug.c
@@ -232,7 +232,6 @@ int perf_quiet_option(void)
 		var++;
 	}
 
-	quiet = true;
 	return 0;
 }
 
-- 
1.7.12.4

  reply	other threads:[~2018-03-13 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 12:31 [PATCH v2 -perf/core 1/2] perf mmap: Discard head in overwrite_rb_find_range Yisheng Xie
2018-03-13 12:31 ` Yisheng Xie [this message]
2018-03-20  6:33   ` [tip:perf/core] perf debug: Avoid setting 'quiet' to 'true' unnecessarily tip-bot for Yisheng Xie
2018-03-16 14:16 ` [PATCH v2 -perf/core 1/2] perf mmap: Discard head in overwrite_rb_find_range Liang, Kan
2018-03-20  6:33 ` [tip:perf/core] perf mmap: Discard head in overwrite_rb_find_range() tip-bot for Yisheng Xie

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=1520944274-37001-2-git-send-email-xieyisheng1@huawei.com \
    --to=xieyisheng1@huawei.com \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).