From: Rufus & Azrael <rufus-azrael@numericable.fr>
To: Marcin Slusarz <marcin.slusarz@gmail.com>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re:[PATCH 0/7] post x86 merge section mismatch fixes
Date: Sun, 12 Oct 2008 12:05:26 +0200 [thread overview]
Message-ID: <48F1CBE6.4030908@numericable.fr> (raw)
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.
reply other threads:[~2008-10-12 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F1CBE6.4030908@numericable.fr \
--to=rufus-azrael@numericable.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox