Commit:     69e97c028b25ef10018d513ead6e7caad276e19f
Parent:     32ed937d0596e849e1976791e78c006cee8356ca
Author:     Sam Ravnborg <[EMAIL PROTECTED]>
AuthorDate: Fri Feb 1 17:49:41 2008 +0100
Committer:  Ingo Molnar <[EMAIL PROTECTED]>
CommitDate: Fri Feb 1 17:49:41 2008 +0100

    x86: silence section mismatch warning in smpboot_64.c
    Silence the following warning:
    WARNING: o-x86_64/arch/x86/kernel/built-in.o(.text+0x17cd3): Section 
mismatch in reference from the function remove_cpu_from_maps() to the variable
    remove_cpu:maps() had a single user: __cpu_disable() so
    mark it static and annotate it with __ref to silence the
    warning from modpost.
    _cpu_disable() has a single user in kernel/cpu.c:
     => take_cpu_down()
        which again has a single user in the following call:
        => __stop_machine_run(take_cpu_down, &tcd_param, cpu);
    Here a kthread is created.
    So maybe the warning is correct and the right fix is to
    remove the __cpuinitdata annotation of cpu_initialized?
    Note: The analysis were disturbed by the fact that we had a variable
          with the same name in cpu/common.c - but this is 32 bit only]
    Note: Should smpboot_64 use cpu_clear()?
    Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
    Cc: "H. Peter Anvin" <[EMAIL PROTECTED]>
    Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
 arch/x86/kernel/smpboot_64.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/smpboot_64.c b/arch/x86/kernel/smpboot_64.c
index cc64b80..d53bd6f 100644
--- a/arch/x86/kernel/smpboot_64.c
+++ b/arch/x86/kernel/smpboot_64.c
@@ -1019,7 +1019,7 @@ static void remove_siblinginfo(int cpu)
        cpu_clear(cpu, cpu_sibling_setup_map);
-void remove_cpu_from_maps(void)
+static void __ref remove_cpu_from_maps(void)
        int cpu = smp_processor_id();
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to