Hi all, After merging the scsi-post-merge tree, today's linux-next build (powerpc allnoconfig, i386 defconfig and others) produced these warnings (I build with CONFIG_DEBUG_SECTION_MISMATCH=y):
WARNING: mm/built-in.o(.text+0x25910): 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+0x25bfc): 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+0x25c5c): 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: mm/built-in.o(.text+0x26194): Section mismatch in reference from the function memblock_reserve_reserved_regions() to the function .init.text:memblock_reserve() The function memblock_reserve_reserved_regions() references the function __init memblock_reserve(). This is often because memblock_reserve_reserved_regions lacks a __init annotation or the annotation of memblock_reserve is wrong. WARNING: mm/built-in.o(.text+0x2630c): Section mismatch in reference from the function memblock_free_reserved_regions() to the function .init.text:memblock_free() The function memblock_free_reserved_regions() references the function __init memblock_free(). This is often because memblock_free_reserved_regions lacks a __init annotation or the annotation of memblock_free is wrong. WARNING: vmlinux.o(.text+0x10190): 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. -- Cheers, Stephen Rothwell s...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/
pgpKVyyXuWYLO.pgp
Description: PGP signature
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
