Message-ID: <1374742433.29835.31.camel@x61.thuisdomein>
Subject: Re: compile x86_64 waring
From: Paul Bolle <pebolle@tiscali.nl>
To: Tom Rini <trini@ti.com>
Cc: Jianpeng Ma <majianpeng@gmail.com>, Rusty Russell <rusty@rustcorp.com.au>,
        tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org
Date: Thu, 25 Jul 2013 10:53:53 +0200
In-Reply-To: <51F061CC.9080704@ti.com>
References: <201307051956052638321@gmail.com>
	 <1374699912.29835.8.camel@x61.thuisdomein> <51F061CC.9080704@ti.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1321
Lines: 34

On Wed, 2013-07-24 at 19:22 -0400, Tom Rini wrote:
> On 07/24/2013 05:05 PM, Paul Bolle wrote:
> > 3) So this looks like a false positive to me (but I'm not at all
> > familiar with, well, the section mismatch checks). Would there be a way
> > to silence this warning? Other than dropping __initdata from
> > numa_nodes_parsed, of course.
> 
> I suspect you have a real problem, in that either numa_nodes_parsed
> needs to not be __initdata (as it's being called by both __init and
> non-__init functions, and hence the problem), or the other caller(s) of
> numa_nodes_parsed need to also be __init.  Is this seen in top-of-tree
> Linus?

Won't v3.11-rc2 do?

> If so, I can take a peek took, if someone shoots me a config
> file.

The relevant config options should be CONFIG_NUMA and CONFIG_ACPI_NUMA
(both are bool, and set to 'y' in my .config).

But I've just pulled top-of-tree Linus, ie commit 07bc9dc1b0
("git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc'"). I'll
try to build that and I 'll send you my .config if this all is still
triggered.


Paul Bolle

--
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/