From: Stephen Rothwell on
Hi all,

After merging the final tree, today's linux-next build (powerpc
allnoconfig with CONFIG_DEBUG_SECTION_MISMATCH=y) produced these warnings:

WARNING: mm/built-in.o(.text+0x24324): Section mismatch in reference from the function memblock_find_in_range() to the function .init.text:memblock_find_base()
The function memblock_find_in_range() references
the function __init memblock_find_base().
This is often because memblock_find_in_range lacks a __init
annotation or the annotation of memblock_find_base is wrong.

WARNING: mm/built-in.o(.text+0x24610): Section mismatch in reference from the function memblock_double_array() to the function .init.text:memblock_free()
The function memblock_double_array() references
the function __init memblock_free().
This is often because memblock_double_array lacks a __init
annotation or the annotation of memblock_free is wrong.

WARNING: mm/built-in.o(.text+0x24670): Section mismatch in reference from the function memblock_double_array() to the function .init.text:memblock_find_base()
The function memblock_double_array() references
the function __init memblock_find_base().
This is often because memblock_double_array lacks a __init
annotation or the annotation of memblock_find_base is wrong.

WARNING: vmlinux.o(.text+0x10264): Section mismatch in reference from the function setup_initial_memory_limit() to the function .init.text:memblock_set_current_limit()
The function setup_initial_memory_limit() references
the function __init memblock_set_current_limit().
This is often because setup_initial_memory_limit lacks a __init
annotation or the annotation of memblock_set_current_limit is wrong.

Introduced by the memblock series in the tip tree.
--
Cheers,
Stephen Rothwell sfr(a)canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
From: Benjamin Herrenschmidt on
On Mon, 2010-08-02 at 14:10 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig with CONFIG_DEBUG_SECTION_MISMATCH=y) produced these warnings:

.../...

> Introduced by the memblock series in the tip tree.

Ok, so those are my fault but none are deadly. I'll do a fixup patch on
top of this.

Cheers,
Ben.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on
Hi Ben,

On Mon, 02 Aug 2010 18:03:50 +1000 Benjamin Herrenschmidt <benh(a)kernel.crashing.org> wrote:
>
> Ok, so those are my fault but none are deadly. I'll do a fixup patch on
> top of this.

OK, thanks.

--
Cheers,
Stephen Rothwell sfr(a)canb.auug.org.au
http://www.canb.auug.org.au/~sfr/