All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [BUG] perf: does not compile on ARM because of Intel PT code
Date: Tue, 1 Sep 2015 10:57:03 +0200	[thread overview]
Message-ID: <20150901085703.GG6315@gmail.com> (raw)
In-Reply-To: <CABPqkBRb0se2N9Rnfv2ajXEq2XTAJY0QUMg1pAk0gHN34fz+Og@mail.gmail.com>


* Stephane Eranian <eranian@google.com> wrote:

> On Tue, Sep 1, 2015 at 1:42 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * Stephane Eranian <eranian@google.com> wrote:
> >
> >> > Ingo just pulled the fix for that a moment ago.  Look for "perf tools: Fix
> >> > build on powerpc broken by pt/bts"
> >> >
> >> Ok, good. I was testing on Linus' tree not tip.git.
> >
> > So that commit was tested on powerpc it appears - mind double checking the ARM
> > build to make sure it's all good?
> >
> Compiles clean on my ARM32 at commit:
> 4c09e0d Merge tag 'perf-urgent-for-mingo' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into
> perf/urgent

Ok, great - will get the fixes to Linus later today.

Thanks,

	Ingo

  parent reply	other threads:[~2015-09-01  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01  8:26 [BUG] perf: does not compile on ARM because of Intel PT code Stephane Eranian
2015-09-01  8:26 ` Adrian Hunter
2015-09-01  8:29   ` Stephane Eranian
2015-09-01  8:42     ` Ingo Molnar
2015-09-01  8:44       ` Stephane Eranian
2015-09-01  8:51         ` Stephane Eranian
2015-09-01  8:57         ` Ingo Molnar [this message]
2015-09-01  8:30 ` Ingo Molnar

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=20150901085703.GG6315@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.