From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Stephane Eranian <eranian@google.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-perf-users@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC PATCH] perf tui: Annotate entries in callchains
Date: Mon, 23 Mar 2015 13:56:39 -0300 [thread overview]
Message-ID: <3FAA059E-DC0F-4290-BDB5-AE2950D1E1CA@gmail.com> (raw)
In-Reply-To: <CABPqkBRee=X_UumuZfW_9d50f1gjFj4NG_rqchityfYjGQvWXw@mail.gmail.com>
Le 23 mars 2015 13:49:24 GMT-03:00, Stephane Eranian <eranian@google.com> a écrit :
>On Sun, Mar 22, 2015 at 5:27 PM, Namhyung Kim <namhyung@kernel.org>
>wrote:().
>>
>> Did you play with acme/perf/core not tip/perf/core? I got same
>> problem but then I realize it's not the Arnaldo's tree. When I
>> changed to acme/perf/core the problem disappeared. :)
>>
>I was only trying it with tip.git. The patch looke simple enough to
>apply
>to tip.git but clearly it relies on some other infrastructure changes
>which
>I don't know about. In my case =, I care about getting this feature in
>tip.git
>or older versions of perf.
It is all in tip.git by now.
>> But unfortunately I got this segfault instead..
Needs a patch that is in perf/urgent
-- Arnaldo
Sent from smartphone.
next prev parent reply other threads:[~2015-03-23 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 22:58 Arnaldo Carvalho de Melo
2015-03-20 0:34 ` Stephane Eranian
[not found] ` <CA+JHD93s2VkkdJMKZOGa6fPwEd43C8Ow80CU0b=bwTV=_8zjhw@mail.gmail.com>
2015-03-20 17:15 ` Stephane Eranian
2015-03-20 17:21 ` Arnaldo Carvalho de Melo
2015-03-20 20:39 ` Arnaldo Carvalho de Melo
2015-03-20 21:07 ` Arnaldo Carvalho de Melo
2015-03-20 21:12 ` Stephane Eranian
2015-03-20 21:34 ` Arnaldo Carvalho de Melo
2015-03-20 21:45 ` Arnaldo Carvalho de Melo
2015-03-23 0:27 ` Namhyung Kim
2015-03-23 16:49 ` Stephane Eranian
2015-03-23 16:56 ` Arnaldo Carvalho de Melo [this message]
2015-03-27 23:05 ` Stephane Eranian
2015-03-28 16:24 ` 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=3FAA059E-DC0F-4290-BDB5-AE2950D1E1CA@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®