From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Shaohua Li <shaohua.li@intel.com>,
Stephane Eranian <eranian@google.com>,
Len Brown <len.brown@intel.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: 2.6.37-rc1: section mismatches
Date: Mon, 1 Nov 2010 14:43:29 +0100 (CET) [thread overview]
Message-ID: <tkrat.725fc810c3a4881e@s5r6.in-berlin.de> (raw)
Three new section mismatches have been introduced:
----
WARNING: vmlinux.o(.text+0x26e8c): Section mismatch in reference from the function tlb_cpuhp_notify() to the function .cpuinit.text:calculate_tlb_offset()
The function tlb_cpuhp_notify() references
the function __cpuinit calculate_tlb_offset().
This is often because tlb_cpuhp_notify lacks a __cpuinit
annotation or the annotation of calculate_tlb_offset is wrong.
apparently due to commit 932967202182743c01a2eee4bdfa2c42697bc586
----
WARNING: vmlinux.o(.text+0x71f47): Section mismatch in reference from the function proc_dowatchdog_enabled() to the variable .init.data:no_watchdog
The function proc_dowatchdog_enabled() references
the variable __initdata no_watchdog.
This is often because proc_dowatchdog_enabled lacks a __initdata
annotation or the annotation of no_watchdog is wrong.
apparently due to commit d9ca07a05ce1c42ac9717e54eaea4546a3a80978
----
WARNING: vmlinux.o(.text+0x17147f): Section mismatch in reference from the function acpi_os_initialize1() to the function .init.text:acpi_osi_setup_late()
The function acpi_os_initialize1() references
the function __init acpi_osi_setup_late().
This is often because acpi_os_initialize1 lacks a __init
annotation or the annotation of acpi_osi_setup_late is wrong.
by merge commit 1bd64d42abdd4f9d44f77011a31f0292112f4c3b or one of the
parents
--
Stefan Richter
-=====-==-=- =-== ----=
http://arcgraph.de/sr/
next reply other threads:[~2010-11-01 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 13:43 Stefan Richter [this message]
2010-11-01 13:53 ` Borislav Petkov
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=tkrat.725fc810c3a4881e@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=eranian@google.com \
--cc=hpa@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.com \
/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
Powered by JetHome