linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM64: perf: wire up perf_regs and unwind support
Date: Thu, 24 Oct 2013 16:50:25 +0200	[thread overview]
Message-ID: <20131024145025.GA1493@krava.redhat.com> (raw)
In-Reply-To: <1382108078-8807-3-git-send-email-jean.pihet@linaro.org>

On Fri, Oct 18, 2013 at 04:54:38PM +0200, Jean Pihet wrote:

SNIP

> +	return -EINVAL;
> +}
> diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
> index 75b93d7..15a69a5 100644
> --- a/tools/perf/config/Makefile
> +++ b/tools/perf/config/Makefile
> @@ -29,11 +29,17 @@ ifeq ($(ARCH),x86_64)
>    NO_PERF_REGS := 0
>    LIBUNWIND_LIBS = -lunwind -lunwind-x86_64
>  endif
> +
>  ifeq ($(ARCH),arm)
>    NO_PERF_REGS := 0
>    LIBUNWIND_LIBS = -lunwind -lunwind-arm
>  endif

I dont see above 'ifeq' in acme's or in tip tree, so hunk
below fails to apply.. what tree was this based on?

otherwise the change looks good to me

jirka

  reply	other threads:[~2013-10-24 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 14:54 [PATCH 0/2] ARM64: perf: add support for the perf registers and dwarf unwinding Jean Pihet
2013-10-18 14:54 ` [PATCH 1/2] ARM64: perf: add support for perf registers API Jean Pihet
2013-10-25 13:14   ` Will Deacon
2013-10-18 14:54 ` [PATCH 2/2] ARM64: perf: wire up perf_regs and unwind support Jean Pihet
2013-10-24 14:50   ` Jiri Olsa [this message]
2013-10-24 16:14     ` Jean Pihet
2013-11-14 11:04 ` [PATCH 0/2] ARM64: perf: add support for the perf registers and dwarf unwinding Sandeepa Prabhu
2013-11-14 11:15   ` Jean Pihet
2013-11-14 11:24     ` Sandeepa Prabhu
2013-11-15 16:42   ` Will Deacon
2013-11-18  5:58     ` Sandeepa Prabhu

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=20131024145025.GA1493@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).