From: Changbin Du <changbin.du@gmail.com>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: Changbin Du <changbin.du@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] perf: support multiple debug options separated by ','
Date: Tue, 26 Nov 2019 22:18:22 +0800 [thread overview]
Message-ID: <20191126141820.kodiejolpyxwz5ck@mail.google.com> (raw)
In-Reply-To: <c22da5eb-71dd-511b-bc9a-4981c3b22d4c@linux.ibm.com>
On Tue, Nov 26, 2019 at 11:10:45AM +0530, Ravi Bangoria wrote:
>
>
> On 11/25/19 8:44 PM, Changbin Du wrote:
> > List of debug variables allowed to set:
> > - verbose - general debug messages
> > - ordered-events - ordered events object debug messages
> > - data-convert - data convert command debug messages
> > - stderr - write debug output (option -v) to stderr
> > - in browser mode
> > - perf-event-open - Print perf_event_open() arguments and
> > - return value
> > + verbose=level - general debug messages
> > + ordered-events=level - ordered events object debug messages
> > + data-convert=level - data convert command debug messages
> > + stderr - write debug output (option -v) to stderr
> > + perf-event-open - Print perf_event_open() arguments and
> > + return value in browser mode
> Shouldn't this be:
>
> stderr - write debug output (option -v) to stderr
> in browser mode
> perf-event-open - Print perf_event_open() arguments and
> return value
>
This is an accident when rebasing. Thank you.
> -Ravi
>
--
Cheers,
Changbin Du
next prev parent reply other threads:[~2019-11-26 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 15:14 [PATCH v6 0/2] perf: add support for logging debug messages to file Changbin Du
2019-11-25 15:14 ` [PATCH v6 1/2] perf: support multiple debug options separated by ',' Changbin Du
2019-11-26 5:40 ` Ravi Bangoria
2019-11-26 14:18 ` Changbin Du [this message]
2019-11-26 9:45 ` Jiri Olsa
2019-11-26 14:34 ` Changbin Du
2019-11-25 15:14 ` [PATCH v6 2/2] perf: add support for logging debug messages to file Changbin Du
2019-11-26 9:50 ` Jiri Olsa
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=20191126141820.kodiejolpyxwz5ck@mail.google.com \
--to=changbin.du@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.