From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Holger Freyther <automatic+kernel@freyther.de>,
linux-kernel@vger.kernel.org,
Holger Hans Peter Freyther <holgar+kernel@google.com>
Subject: Re: [RFC 0/6] perf probe: Attempt to improve C++ probing
Date: Tue, 15 May 2018 11:10:43 -0300 [thread overview]
Message-ID: <20180515141043.GG2917@kernel.org> (raw)
In-Reply-To: <20180514223107.3ff9d8249ef41b8dd2957591@kernel.org>
Em Mon, May 14, 2018 at 10:31:07PM +0900, Masami Hiramatsu escreveu:
> On Mon, 14 May 2018 12:19:34 +0800 Holger Freyther <automatic+kernel@freyther.de> wrote:
> > ./perf probe -x . -V "std::vector<int, std::allocator<int> >::size%return"
> OK, this series looks good to me :)
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
> for this series.
> Arnaldo, could you pull this series?
Sure, I'm just waiting for Holger to comment on Namhyung points,
Thanks,
- Arnaldo
next prev parent reply other threads:[~2018-05-15 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 4:19 [RFC 0/6] perf probe: Attempt to improve C++ probing Holger Freyther
2018-05-14 4:19 ` [RFC 1/6] perf probe: Do not exclude mangled C++ funcs Holger Freyther
2018-05-14 4:19 ` [RFC 2/6] perf probe: Parse linerange for C++ functions Holger Freyther
2018-05-14 4:19 ` [RFC 3/6] perf probe: Make listing of C++ functions work Holger Freyther
2018-05-14 4:19 ` [RFC 4/6] perf probe: Show variables for C++ functions Holger Freyther
2018-05-14 4:19 ` [RFC 5/6] perf probe: Make listing of variables work " Holger Freyther
2018-05-14 4:19 ` [RFC 6/6] perf probe: Make it possible to add a C++ uprobe Holger Freyther
2018-05-14 13:08 ` [RFC 0/6] perf probe: Attempt to improve C++ probing Masami Hiramatsu
2018-05-14 13:31 ` Masami Hiramatsu
2018-05-15 14:10 ` Arnaldo Carvalho de Melo [this message]
[not found] <20180513110617.91669-1-automatic+kernel@freyther.de>
2018-05-14 16:11 ` Arnaldo Carvalho de Melo
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=20180515141043.GG2917@kernel.org \
--to=acme@kernel.org \
--cc=automatic+kernel@freyther.de \
--cc=holgar+kernel@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.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 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.