Date: Thu, 26 Jan 2006 17:36:50 -0800
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Andi Kleen <ak@muc.de>
Cc: ashok.raj@intel.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
       kaos@sgi.com, randy.d.dunlap@intel.com
Subject: Re: wrongly marked __init/__initdata for CPU hotplug
Message-Id: <20060126173650.51496925.rdunlap@xenotime.net>
In-Reply-To: <20060126042603.GA88680@muc.de>
References: <20060125120253.A30999@unix-os.sc.intel.com>
	<20060126042603.GA88680@muc.de>
Organization: YPO4
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 842
Lines: 22

On 26 Jan 2006 05:26:03 +0100 Andi Kleen wrote:

> On Wed, Jan 25, 2006 at 12:02:53PM -0800, Ashok Raj wrote:
> > Hi Andrew
> > 
> > attached patch is 2 more cases i found via running the reference_init.pl
> > script. These were easy to spot just knowing the file names. There is 
> > one another about init/main.c that i cant exactly zero in. (partly 
> > because i dont know how to interpret the data thats spewed out of the tool).
> 
> I think that's the reference to __initcall_start / end 
> That one is unavoidable, but not a bug.

Yes, that's the conclusion that I came to also.

---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/