From: Kevin Winchester <kjwinchester@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Linux Kernel Mailing List \\" <linux-kernel@vger.kernel.org>
Subject: Section mismatch warnings with current mainline git
Date: Wed, 07 May 2008 20:43:32 -0300 [thread overview]
Message-ID: <48223EA4.4010306@gmail.com> (raw)
Is this something people are interested in seeing?
WARNING: vmlinux.o(.text+0x1422b): Section mismatch in reference from
the function set_pte_phys() to the function .init.text:spp_getpage()
The function set_pte_phys() references
the function __init spp_getpage().
This is often because set_pte_phys lacks a __init
annotation or the annotation of spp_getpage is wrong.
WARNING: vmlinux.o(.text+0x1429a): Section mismatch in reference from
the function set_pte_phys() to the function .init.text:spp_getpage()
The function set_pte_phys() references
the function __init spp_getpage().
This is often because set_pte_phys lacks a __init
annotation or the annotation of spp_getpage is wrong.
WARNING: vmlinux.o(.text+0x17c72): Section mismatch in reference from
the function arch_setup_additional_pages() to the variable
.init.data:vdso_end
The function arch_setup_additional_pages() references
the variable __initdata vdso_end.
This is often because arch_setup_additional_pages lacks a __initdata
annotation or the annotation of vdso_end is wrong.
WARNING: vmlinux.o(.text+0x17c79): Section mismatch in reference from
the function arch_setup_additional_pages() to the variable
.init.data:vdso_start
The function arch_setup_additional_pages() references
the variable __initdata vdso_start.
This is often because arch_setup_additional_pages lacks a __initdata
annotation or the annotation of vdso_start is wrong.
WARNING: vmlinux.o(.cpuinit.text+0x2497): Section mismatch in reference
from the function uv_cpu_init() to the function .init.text:uv_system_init()
The function __cpuinit uv_cpu_init() references
a function __init uv_system_init().
If uv_system_init is only used by uv_cpu_init then
annotate uv_system_init with a matching annotation.
--
Kevin Winchester
reply other threads:[~2008-05-07 23:43 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=48223EA4.4010306@gmail.com \
--to=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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