All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: David Rientjes <rientjes@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Jiri Olsa <jolsa@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <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 10:49:09 +0200	[thread overview]
Message-ID: <20130416084909.GA8404@gmail.com> (raw)
In-Reply-To: <CABPqkBSzyswo+bWoESsXufi-OBw820m6iQ3ztE12H5XXRtFiDw@mail.gmail.com>


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

> On Tue, Apr 16, 2013 at 9:52 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * 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?
> >
>
> To make backport clean, I need to generate a patch against a kernel git tree 
> which does not have the PEBS-LL (LDLAT) support. tip.git already has PEBS-LL, so 
> I need to use another tree.

You can just use the tip:perf/urgent branch for that, it does not have the LDLAT 
patches. But using Linus's tree is fine as a base too.

Thanks,

	Ingo

      reply	other threads:[~2013-04-16  8:49 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
2013-04-16  8:18   ` Stephane Eranian
2013-04-16  8:49     ` Ingo Molnar [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=20130416084909.GA8404@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.