public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Tony Battersby <tonyb@cybernetics.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Vince Weaver <vincent.weaver@maine.edu>,
	Ingo Molnar <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: lk 4.5 oops on boot with Xeon D-1520
Date: Wed, 24 Feb 2016 18:41:27 +0100	[thread overview]
Message-ID: <20160224174127.GM6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F0770589D374@SHSMSX103.ccr.corp.intel.com>

On Wed, Feb 24, 2016 at 04:36:33PM +0000, Liang, Kan wrote:
> > 
> > Thanks, that fixes it.
> > 
> > Note: your patch appears to be against linux-next.  I had to change
> > "arch/x86/events/intel/uncore_snbep.c" to
> > "arch/x86/kernel/cpu/perf_event_intel_uncore_snbep.c" for the patch to
> > apply against current linux-git.
> 
> Thanks for the verification.
> 
> I think the perf related code just moved to a new place "arch/x86/events/".
> So the patch is based on that new place.
> 
> Peter, should I resend the patch for the old place?

Nah, I'll sort it out. Thanks!

  reply	other threads:[~2016-02-24 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 22:51 PROBLEM: lk 4.5 oops on boot with Xeon D-1520 Tony Battersby
2016-02-24  9:11 ` Thomas Gleixner
2016-02-24 15:37   ` Liang, Kan
2016-02-24 16:31     ` Tony Battersby
2016-02-24 16:36       ` Liang, Kan
2016-02-24 17:41         ` Peter Zijlstra [this message]
2016-02-29 11:02     ` [tip:perf/core] perf/x86/intel/uncore: Remove SBOX support for BDX-DE tip-bot for Kan Liang

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=20160224174127.GM6356@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tonyb@cybernetics.com \
    --cc=vincent.weaver@maine.edu \
    /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