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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
