From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Latest GIT section mismatches
Date: Fri, 17 Oct 2008 13:15:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810171314360.685@shark.he.net> (raw)
In-Reply-To: <b637ec0b0810171312y2bc88085o7973c257713b0d5c@mail.gmail.com>
On Fri, 17 Oct 2008, Fabio Comolli wrote:
> Linus ' GIT 2.6.27-05323-g26e9a39 (pulled less than one hour ago) gives:
>
> WARNING: vmlinux.o(.text+0x1cde2): Section mismatch in reference from
> the function reserve_region_with_split() to the function
> .init.text:__reserve_region_with_split()
> The function reserve_region_with_split() references
> the function __init __reserve_region_with_split().
> This is often because reserve_region_with_split lacks a __init
> annotation or the annotation of __reserve_region_with_split is wrong.
>
> WARNING: vmlinux.o(.cpuinit.text+0xeec): Section mismatch in reference
> from the function cpu_init() to the function
> .init.text:init_thread_xstate()
> The function __cpuinit cpu_init() references
> a function __init init_thread_xstate().
> If init_thread_xstate is only used by cpu_init then
> annotate init_thread_xstate with a matching annotation.
>
> WARNING: vmlinux.o(.cpuinit.data+0x0): Section mismatch in reference
> from the variable initial_code to the function
> .init.text:i386_start_kernel()
> The variable __cpuinitdata initial_code references
> a function __init i386_start_kernel().
> If i386_start_kernel is only used by initial_code then
> annotate i386_start_kernel with a matching annotation.
so on i386.
Did you build with CONFIG_DEBUG_SECTION_MISMATCH=y ?
> I'll send .config on request.
--
~Randy
prev parent reply other threads:[~2008-10-17 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 20:12 Fabio Comolli
2008-10-17 20:15 ` Randy.Dunlap [this message]
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=Pine.LNX.4.64.0810171314360.685@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®