All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexis Berlemont <alexis.berlemont@gmail.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com
Subject: Re: [PATCH] perf: check that objdump correctly works
Date: Tue, 6 Dec 2016 11:44:57 -0300	[thread overview]
Message-ID: <20161206144457.GA2399@kernel.org> (raw)
In-Reply-To: <20161201000436.10354-1-alexis.berlemont@gmail.com>

Em Thu, Dec 01, 2016 at 01:04:35AM +0100, Alexis Berlemont escreveu:
> Hi,
> 
> In perf todo list, there was an entry regarding objdump:
> 
> * Check if the objdump call in annotate worked or not, providing a
>   popup window telling it didn't work, to test, just uninstall
>   binutils or otherwise remove objdump from the path.
> 
> The patch below tries to fulfill that point.

Thanks for working on this, will try and process it ASAP.

- Arnaldo
 
> Alexis.
> 
> Alexis Berlemont (1):
>   perf annotate: check that objdump correctly works
> 
>  tools/perf/util/annotate.c | 79 +++++++++++++++++++++++++++++++++++++++++++++-
>  tools/perf/util/annotate.h |  3 ++
>  2 files changed, 81 insertions(+), 1 deletion(-)
> 
> -- 
> 2.10.2

      parent reply	other threads:[~2016-12-06 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  0:04 [PATCH] perf: check that objdump correctly works Alexis Berlemont
2016-12-01  0:04 ` [PATCH] perf annotate: " Alexis Berlemont
2016-12-06 19:38   ` Arnaldo Carvalho de Melo
2016-12-09 23:57     ` Alexis Berlemont
2016-12-20  0:11     ` [PATCH v2 0/1] perf: " Alexis Berlemont
2016-12-20  0:11     ` [PATCH v2 1/1] perf annotate: " Alexis Berlemont
2016-12-06 14:44 ` 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=20161206144457.GA2399@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexis.berlemont@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 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.