[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290702852.2145.60.camel@laptop>
Date: Thu, 25 Nov 2010 17:34:12 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Will Deacon <will.deacon@....com>
Cc: Ingo Molnar <mingo@...e.hu>, Lin Ming <ming.m.lin@...el.com>,
Stephane Eranian <eranian@...gle.com>,
"robert.richter" <robert.richter@....com>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
fweisbec <fweisbec@...il.com>, paulus <paulus@...ba.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Kay Sievers <kay.sievers@...y.org>,
"H. Peter Anvin" <hpa@...or.com>,
Kyle Moffett <kyle@...fetthome.net>,
linux-kernel@...r.kernel.org, davem <davem@...emloft.net>,
Michael Cree <mcree@...on.net.nz>,
Deng-Cheng Zhu <dengcheng.zhu@...il.com>,
Paul Mundt <lethal@...ux-sh.org>,
Don Zickus <dzickus@...hat.com>
Subject: Re: [RFC][PATCH 2/8] perf, arch: Use early_initcall() for all arch
pmu implementations
On Thu, 2010-11-25 at 16:22 +0000, Will Deacon wrote:
> What tree/branch are these patches taken against? They don't seem
> to apply against -rc3 or tip/master.
tip/master + my quilt queue
> Anyway, I currently have some
> pending patches to split up the monolithic perf_event.c we have for ARM
> so that different PMU implementations can live in different files (in
> the same way that x86 does it). This might mean that your initcall patch
> no longer applies because it will be a couple of thousand lines higher
> up in the file.
That's ok, I'm sure we can sort that out when I've got stuff working ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists