From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang YanQing <udknight@gmail.com>,
jolsa@redhat.com, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf report: Provide libtraceevent with a kernel symbol resolver
Date: Tue, 6 Mar 2018 11:01:17 -0300 [thread overview]
Message-ID: <20180306140117.GB10176@kernel.org> (raw)
In-Reply-To: <20180306073658.GA7964@udknight>
Em Tue, Mar 06, 2018 at 03:36:58PM +0800, Wang YanQing escreveu:
> On Thu, Feb 08, 2018 at 01:20:31PM +0100, Jiri Olsa wrote:
> > On Mon, Jan 15, 2018 at 12:47:32PM +0800, Wang YanQing wrote:
> > > So that beautifiers wanting to resolve kernel function addresses to
> > > names can do its work, and when we use "perf report" for output of
> > > "perf kmem record", we will get kernel symbol output.
> > >
> > > Signed-off-by: Wang YanQing <udknight@gmail.com>
> >
> > Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> Hi! Arnaldo Carvalho de Melo
>
> What is the status of this patch now?
> Does the patch sanked to the bottom of your mailbox?
It looks ok, but you forgot to add a before and after output of tools
affected by the patch.
Reading the patch one can try and figure out how to test your patch, but
if you show how the output is changed, providing the exact command line
used to produce the output, then you will make it easier for reviewers
to reproduce your results, testing your patch.
I try to do this for every patch, so it all adds up, please help me with
reviewing your patch :-)
- Arnaldo
prev parent reply other threads:[~2018-03-06 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 4:47 [PATCH] perf report: Provide libtraceevent with a kernel symbol resolver Wang YanQing
2018-01-15 10:06 ` Jiri Olsa
2018-01-16 16:48 ` Wang YanQing
2018-01-18 9:43 ` Jiri Olsa
2018-01-18 14:22 ` Wang YanQing
2018-01-19 18:57 ` Jiri Olsa
2018-01-21 17:25 ` Wang YanQing
2018-01-23 12:41 ` Jiri Olsa
2018-02-08 12:20 ` Jiri Olsa
2018-03-06 7:36 ` Wang YanQing
2018-03-06 14:01 ` 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=20180306140117.GB10176@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=udknight@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox