[<prev] [next>] [day] [month] [year] [list]
Message-ID: <48F1CBE6.4030908@numericable.fr>
Date: Sun, 12 Oct 2008 12:05:26 +0200
From: Rufus & Azrael <rufus-azrael@...ericable.fr>
To: Marcin Slusarz <marcin.slusarz@...il.com>,
Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re:[PATCH 0/7] post x86 merge section mismatch fixes
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists