Re:[PATCH 0/7] post x86 merge section mismatch fixes
From: Rufus & Azrael
Date: Sun Oct 12 2008 - 05:58:26 EST
Hello Marcin,
I have applied your patches on my fresh 2.6.27-git2 kernel and the
section mismatches are now fixed, just remaining the following:
WARNING: arch/x86/kernel/built-in.o(.cpuinit.text+0x347): Section
mismatch in reference from the function fpu_init() to the function
.init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.
WARNING: kernel/built-in.o(.text+0x10690): Section mismatch in
reference from the function notify_cpu_starting() to the variable
.cpuinit.data:cpu_chain
The function notify_cpu_starting() references
the variable __cpuinitdata cpu_chain.
This is often because notify_cpu_starting lacks a __cpuinitdata
annotation or the annotation of cpu_chain is wrong.
WARNING: vmlinux.o(.text+0x33264): Section mismatch in reference from
the function notify_cpu_starting() to the variable .cpuinit.data:cpu_chain
The function notify_cpu_starting() references
the variable __cpuinitdata cpu_chain.
This is often because notify_cpu_starting lacks a __cpuinitdata
annotation or the annotation of cpu_chain is wrong.
WARNING: vmlinux.o(.cpuinit.text+0x605): Section mismatch in reference
from the function fpu_init() to the function
.init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.
Thanks and regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/