Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-18 Thread Sam Ravnborg
On Sun, Feb 17, 2008 at 09:38:55PM +0100, Geert Uytterhoeven wrote: > On Sun, 17 Feb 2008, Sam Ravnborg wrote: > > On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: > > > On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: > > > > On m68k (CONFIG_SPARSEMEM is not set), I get: > > > >

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-18 Thread Sam Ravnborg
On Sun, Feb 17, 2008 at 09:38:55PM +0100, Geert Uytterhoeven wrote: On Sun, 17 Feb 2008, Sam Ravnborg wrote: On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: On m68k (CONFIG_SPARSEMEM is not set), I get:

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Sam Ravnborg
> > > I would need a config where the mismatch triggers for one > > of the more popular architectures (as in where I have a toolchain). > > That was with plain m68k defconfig. > > > I could not reproduce it with x86 64bit - not even with > > -fno-inline-functions > > If it helps, my

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On Sun, 17 Feb 2008, Sam Ravnborg wrote: > On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: > > On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: > > > On m68k (CONFIG_SPARSEMEM is not set), I get: > > > > > > WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in > > >

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Sam Ravnborg
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: > On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: > > On m68k (CONFIG_SPARSEMEM is not set), I get: > > > > WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference > > from the function free_area_init_core() to

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: > On m68k (CONFIG_SPARSEMEM is not set), I get: > > WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference > from the function free_area_init_core() to the function > .init.text:setup_usemap() > The function __meminit

[PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On m68k (CONFIG_SPARSEMEM is not set), I get: WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from the function free_area_init_core() to the function .init.text:setup_usemap() The function __meminit free_area_init_core() references a function __init

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: On m68k (CONFIG_SPARSEMEM is not set), I get: WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from the function free_area_init_core() to the function .init.text:setup_usemap() The function __meminit

[PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On m68k (CONFIG_SPARSEMEM is not set), I get: WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from the function free_area_init_core() to the function .init.text:setup_usemap() The function __meminit free_area_init_core() references a function __init

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Sam Ravnborg
On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: On m68k (CONFIG_SPARSEMEM is not set), I get: WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from the function free_area_init_core() to the

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Geert Uytterhoeven
On Sun, 17 Feb 2008, Sam Ravnborg wrote: On Sun, Feb 17, 2008 at 01:31:14PM +0100, Geert Uytterhoeven wrote: On Sun, 17 Feb 2008, Geert Uytterhoeven wrote: On m68k (CONFIG_SPARSEMEM is not set), I get: WARNING: vmlinux.o(.meminit.text+0x36c): Section mismatch in reference from

Re: [PATCH] mm: setup_usemap() must be __meminit

2008-02-17 Thread Sam Ravnborg
I would need a config where the mismatch triggers for one of the more popular architectures (as in where I have a toolchain). That was with plain m68k defconfig. I could not reproduce it with x86 64bit - not even with -fno-inline-functions If it helps, my cross-compiler is gcc