LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Miles Lane <miles.lane@gmail.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-rc4-mm1 + 3 hot-fixes -- WARNING: could not find versions for .tmp_versions/built-in.mod
Date: Fri, 23 Mar 2007 21:54:29 +0900 [thread overview]
Message-ID: <20070323214418.3F04.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20070320212705.GB13349@uranus.ravnborg.org>
Hello.
> > WARNING: mm/built-in.o - Section mismatch: reference to
> > .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at
> > offset 0x15c8f) and '__section_nr'
> I took a look at this one.
> You have SPARSEMEM enabled in your config.
> And then I see that in sparse.c we call alloc_bootmem_node()
> from a function I thought should be marked __devinit (it
> is used by memory_hotplug.c).
> But I am not familiar enough to judge if __alloc_bootmen_node
> are marked correct with __init or __devinit (to say
> this is used in the HOTPLUG case) is more correct.
> Anyone?
>
> > WARNING: mm/built-in.o - Section mismatch: reference to
> > .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at
> > offset 0x15d02) and '__section_nr'
> Same as above....
Memory hotplug code has __meminit for its purpose.
But, I suspect that many other places of memory hotplug code may have
same issue. I will chase them.
BTW, does -mm code checks more strict than stock kernel? I can't see
these warnings in 2.6.21-rc4.....
Bye.
--
Yasunori Goto
next prev parent reply other threads:[~2007-03-23 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 14:35 Miles Lane
2007-03-20 16:11 ` Andrew Morton
2007-03-20 20:35 ` Sam Ravnborg
2007-03-20 21:27 ` Sam Ravnborg
2007-03-23 12:54 ` Yasunori Goto [this message]
2007-03-23 16:19 ` Sam Ravnborg
2007-03-29 5:17 ` [RFC:PATCH]regster memory init functions into white list of section mismatch Yasunori Goto
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=20070323214418.3F04.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=sam@ravnborg.org \
--subject='Re: 2.6.21-rc4-mm1 + 3 hot-fixes -- WARNING: could not find versions for .tmp_versions/built-in.mod' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).