From: Ingo Molnar <mingo@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Stephane Eranian <eranian@google.com>,
Peter Zijlstra <peterz@infradead.org>,
jolsa@redhat.com, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [build error] perf/urgent broken due to INTEL_UEVENT_PEBS_LDLAT_EXTRA_REG
Date: Tue, 16 Apr 2013 09:52:12 +0200 [thread overview]
Message-ID: <20130416075212.GA6565@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304152002150.3952@chino.kir.corp.google.com>
* David Rientjes <rientjes@google.com> wrote:
> Commit 3de4ad210387 ("perf/x86: Fix offcore_rsp valid mask for SNB/IVB") in
> perf/urgent breaks the build:
Hm, that's was me resolving the conflicts incorrectly.
Stephane, mind sending a tested version of the patch against current -git that can
be applied to v3.9 and can be backported?
Thanks,
Ingo
next prev parent reply other threads:[~2013-04-16 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 3:07 [build error] perf/urgent broken due to INTEL_UEVENT_PEBS_LDLAT_EXTRA_REG David Rientjes
2013-04-16 7:52 ` Ingo Molnar [this message]
2013-04-16 8:18 ` Stephane Eranian
2013-04-16 8:49 ` 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=20130416075212.GA6565@gmail.com \
--to=mingo@kernel.org \
--cc=eranian@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
/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.