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
Subject: Re: compile x86_64 waring
Date: Thu, 25 Jul 2013 10:53:53 +0200 [thread overview]
Message-ID: <1374742433.29835.31.camel@x61.thuisdomein> (raw)
In-Reply-To: <51F061CC.9080704@ti.com>
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
next prev parent reply other threads:[~2013-07-25 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 11:56 compile x86_64 waring majianpeng
2013-07-24 21:05 ` Paul Bolle
2013-07-24 23:22 ` Tom Rini
2013-07-25 8:53 ` Paul Bolle [this message]
2013-07-25 9:41 ` Paul Bolle
2013-07-25 12:17 ` Tom Rini
2013-10-30 13:04 ` Leon Gorge
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=1374742433.29835.31.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=majianpeng@gmail.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=trini@ti.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.