memblock: Annotate memblock functions with __init_memblock

Stephen found

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

So let memblock_find_region() to use __init_memblock instead of __init
directly.

Also fix one function that did not have __init* to be __init_memblock.

Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
LKML-Reference: <4CB366B1.40405@kernel.org>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>

authored by Yinghai Lu and committed by H. Peter Anvin cd79481d 236260b9

+2 -2
+2 -2
mm/memblock.c
··· 99 99 * are top-down. 100 100 */ 101 101 102 - static phys_addr_t __init memblock_find_region(phys_addr_t start, phys_addr_t end, 102 + static phys_addr_t __init_memblock memblock_find_region(phys_addr_t start, phys_addr_t end, 103 103 phys_addr_t size, phys_addr_t align) 104 104 { 105 105 phys_addr_t base, res_base; ··· 653 653 } 654 654 } 655 655 656 - static int memblock_search(struct memblock_type *type, phys_addr_t addr) 656 + static int __init_memblock memblock_search(struct memblock_type *type, phys_addr_t addr) 657 657 { 658 658 unsigned int left = 0, right = type->cnt; 659 659