linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: He Kuang <hekuang@huawei.com>,
	a.p.zijlstra@chello.nl, mingo@redhat.com, namhyung@kernel.org,
	wangnan0@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] perf probe: Fix failure to add multiple probes without debuginfo
Date: Sat, 21 Mar 2015 14:54:21 -0300	[thread overview]
Message-ID: <20150321175421.GT16485@kernel.org> (raw)
In-Reply-To: <550D61C9.10002@hitachi.com>

Em Sat, Mar 21, 2015 at 09:19:21PM +0900, Masami Hiramatsu escreveu:
> (2015/03/20 22:50), Arnaldo Carvalho de Melo wrote:
> > Em Fri, Mar 20, 2015 at 04:42:46PM +0900, Masami Hiramatsu escreveu:
> >> OK, I've checked that this solve the problem :)

> >> Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>

> > Ok, next time, please consider sending a Tested-by: tag instead, if what
> > you did was to apply the patch, check that it fixes the problem, that
> > provides a stronger patch endorsement.

> I see. :)
> 
> Tested-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>

Thanks!
 
> BTW, I've found another bug in perf probe for these sys_XXX functions.

Ooops, 

<SNIP>
 
> Something went wrong... :-( I'll check that.

Thanks again!

- Arnaldo

  reply	other threads:[~2015-03-21 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  9:23 [PATCH] perf probe: Fix failure to add multiple probes without debuginfo He Kuang
2015-03-19 10:02 ` He Kuang
2015-03-19 13:59   ` Arnaldo Carvalho de Melo
2015-03-20  1:56     ` [PATCHv2] " He Kuang
2015-03-20  7:42       ` Masami Hiramatsu
2015-03-20 13:50         ` Arnaldo Carvalho de Melo
2015-03-21 12:19           ` Masami Hiramatsu
2015-03-21 17:54             ` Arnaldo Carvalho de Melo [this message]
2015-03-22 10:14       ` [tip:perf/core] " tip-bot for He Kuang

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=20150321175421.GT16485@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hekuang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=wangnan0@huawei.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;
as well as URLs for NNTP newsgroup(s).