public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
	acme@infradead.org, eranian@google.com, andi@firstfloor.org
Subject: Re: [PATCH] perf/x86/uncore: split Intel uncore driver to smaller files
Date: Mon, 28 Jul 2014 16:05:45 +0800	[thread overview]
Message-ID: <53D60459.8040702@intel.com> (raw)
In-Reply-To: <20140728075623.GP19379@twins.programming.kicks-ass.net>

On 07/28/2014 03:56 PM, Peter Zijlstra wrote:
> On Fri, Jul 25, 2014 at 04:40:55PM +0800, Yan, Zheng wrote:
>> split Intel uncore driver into four files:
>>  - perf_event_intel_uncore.c: general functions of Intel uncore driver.
>>  - perf_event_intel_uncore_nhmex.c: hardware specific code for
>>    Nehalem-EX/Westmere-EX
>>  - perf_event_intel_uncore_snb.c: hardware specific code for
>>    Nehalem/SandBridge/Haswell
>>  - perf_event_intel_uncore_snbep.c: hardware specific code for
>>    SandyBridge-EP/IvyTown uncore
> 
> Did not apply properly to tip/master, also can you do that in 3 patches?
> 

the patch is based on tip/perf/core

> One breaking out the nhm/wsm-ex part, one breaking out the
> nhm/wsm/snb/ivb/hsw bits, and one for the snb/ivb-ep bits?
>
will do

Regards
Yan, Zheng

  reply	other threads:[~2014-07-28  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  8:40 [PATCH] perf/x86/uncore: split Intel uncore driver to smaller files Yan, Zheng
2014-07-28  7:56 ` Peter Zijlstra
2014-07-28  8:05   ` Yan, Zheng [this message]
2014-07-28  8:53     ` Peter Zijlstra
2014-07-29 14:41       ` Stephane Eranian

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=53D60459.8040702@intel.com \
    --to=zheng.z.yan@intel.com \
    --cc=acme@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox