Skip to contentSkip to conversation

x86: make setup_xstate_init() __init

PATCH Applied Alexey Dobriyan 2 participants 2 messages Aug 30, 2008 – Sep 6, 2008 x86

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 x86: make setup_xstate_init() __init

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

---

 arch/x86/kernel/xsave.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kernel/xsave.c +1 -1
@@ -272,7 +272,7 @@ void __cpuinit xsave_init(void)
 /*
  * setup the xstate image representing the init state
  */
-void setup_xstate_init(void)
+static void __init setup_xstate_init(void)
 {
 	init_xstate_buf = alloc_bootmem(xstate_size);
 	init_xstate_buf->i387.mxcsr = MXCSR_DEFAULT;
Applied
#1 lore raw
Quoted 9 lines · Alexey Dobriyan

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

---

 arch/x86/kernel/xsave.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

applied to tip/x86/xsave, thanks Alexey.

Ingo