diff options
author | Sam Ravnborg <sam@ravnborg.org> | 2008-02-01 19:49:42 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-02-01 19:49:42 +0300 |
commit | c72258c7c9de448d5ea826ec6b4737eccbaa6718 (patch) | |
tree | 718d9a53c535e92ccd59f9f50d33a2421d9d5953 /drivers/ieee1394/hosts.h | |
parent | 69e97c028b25ef10018d513ead6e7caad276e19f (diff) | |
download | linux-c72258c7c9de448d5ea826ec6b4737eccbaa6718.tar.xz |
x86: fix section mismatch warnings when referencing notifiers
Fix the following warnings:
WARNING: arch/x86/kernel/built-in.o(.exit.text+0xf8): Section mismatch in reference from the function msr_exit() to the variable .cpuinit.data:msr_class_cpu_notifier
WARNING: arch/x86/kernel/built-in.o(.exit.text+0x158): Section mismatch in reference from the function cpuid_exit() to the variable .cpuinit.data:cpuid_class_cpu_notifier
WARNING: arch/x86/kernel/built-in.o(.exit.text+0x171): Section mismatch in reference from the function microcode_exit() to the variable .cpuinit.data:mc_cpu_notifier
In all three cases there were a function annotated __exit
that referenced a variable annotated __cpuinitdata.
The fix was to replace the annotation of the notifier
with __refdata to tell modpost that the reference to
a _cpuinit function in the notifier are OK.
The unregister call that references the notifier
variable will simple delete the function pointer
so there is no problem ignoring the reference.
Note: This looks like another case where __cpuinit
has been used as replacement for proper use
of CONFIG_HOTPLUG_CPU to decide what code are used for
HOTPLUG_CPU.
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/ieee1394/hosts.h')
0 files changed, 0 insertions, 0 deletions