Commit-ID:  ef11dadb8373fcbe53bdd09ceb262b2f18da10c5
Gitweb:     http://git.kernel.org/tip/ef11dadb8373fcbe53bdd09ceb262b2f18da10c5
Author:     Dongsheng Yang <[email protected]>
AuthorDate: Wed, 5 Mar 2014 17:58:36 +0800
Committer:  Ingo Molnar <[email protected]>
CommitDate: Tue, 11 Mar 2014 11:57:56 +0100

perf/x86/uncore: Add __init for uncore_cpumask_init()

Commit:

  411cf180fa00 perf/x86/uncore: fix initialization of cpumask

introduced the function uncore_cpumask_init(), which is only
called in __init intel_uncore_init(). But it is not marked
with __init, which produces the following warning:

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

This patch marks uncore_cpumask_init() with __init.

Signed-off-by: Dongsheng Yang <[email protected]>
Acked-by: Stephane Eranian <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
Cc: Paul Mackerras <[email protected]>
Cc: Arnaldo Carvalho de Melo <[email protected]>
Cc: "H. Peter Anvin" <[email protected]>
Link: 
http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
---
 arch/x86/kernel/cpu/perf_event_intel_uncore.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kernel/cpu/perf_event_intel_uncore.c 
b/arch/x86/kernel/cpu/perf_event_intel_uncore.c
index b262c61..5c2537a 100644
--- a/arch/x86/kernel/cpu/perf_event_intel_uncore.c
+++ b/arch/x86/kernel/cpu/perf_event_intel_uncore.c
@@ -4229,7 +4229,7 @@ static int __init uncore_pmus_register(void)
        return 0;
 }
 
-static void uncore_cpumask_init(void)
+static void __init uncore_cpumask_init(void)
 {
        int cpu;
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to