With some compilers/configs fadump_setup_param_area() isn't inlined into
its caller (which is __init), leading to a section mismatch warning:
WARNING: modpost: vmlinux: section mismatch in reference:
fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area)
-> memblock_phys_alloc_range (section: .init.text)
Fix it by adding an __init annotation.
Fixes: 683eab94da75 ("powerpc/fadump: setup additional parameters for dump
capture kernel")
Reported-by: Stephen Rothwell <s...@canb.auug.org.au>
Closes: https://lore.kernel.org/all/20240515163708.3380c...@canb.auug.org.au/
Reported-by: kernel test robot <l...@intel.com>
Closes: https://lore.kernel.org/all/202405140922.ouclox4y-...@intel.com/
Signed-off-by: Michael Ellerman <m...@ellerman.id.au>
---
arch/powerpc/kernel/fadump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
index 2276bacc4170..60f974775fc8 100644
--- a/arch/powerpc/kernel/fadump.c
+++ b/arch/powerpc/kernel/fadump.c
@@ -1740,7 +1740,7 @@ static void __init fadump_process(void)
* Reserve memory to store additional parameters to be passed
* for fadump/capture kernel.
*/
-static void fadump_setup_param_area(void)
+static void __init fadump_setup_param_area(void)
{
phys_addr_t range_start, range_end;
--
2.45.0
