From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
Chad Paradis <chad.paradis@umit.maine.edu>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [patch] perf tools: perf list broken on ARM
Date: Thu, 9 Jan 2014 10:02:28 +0100 [thread overview]
Message-ID: <20140109090228.GD7572@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1401081629200.4410@vincent-weaver-1.um.maine.edu>
On Wed, Jan 08, 2014 at 04:30:17PM -0500, Vince Weaver wrote:
>
> just checking on the status of this patch. Am I sending it to the wrong
> place? Did it get lost in the post-holiday e-mail purges?
>
> The bug is annoying if you're trying to use perf on ARM systems.
Its for acme and he seems on the Cc, I suppose you got stuck in the
holiday backlog.
next prev parent reply other threads:[~2014-01-09 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 20:39 [patch] perf tools: perf list broken on ARM Vince Weaver
2014-01-08 21:30 ` Vince Weaver
2014-01-09 8:17 ` Namhyung Kim
2014-01-09 12:12 ` Arnaldo Carvalho de Melo
2014-01-09 12:37 ` Namhyung Kim
2014-01-09 12:48 ` Arnaldo Carvalho de Melo
2014-02-05 20:34 ` Vince Weaver
2014-02-06 13:38 ` Arnaldo Carvalho de Melo
2014-01-09 9:02 ` Peter Zijlstra [this message]
2014-02-22 17:55 ` [tip:perf/core] perf list: Fix checking for supported events on older kernels tip-bot for Vince Weaver
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 21:58 [patch] perf tools: perf list broken on ARM Vince Weaver
2013-12-10 2:11 ` Namhyung Kim
2013-12-10 3:58 ` Vince Weaver
2013-12-10 5:08 ` Namhyung Kim
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=20140109090228.GD7572@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=chad.paradis@umit.maine.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=vincent.weaver@maine.edu \
/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