public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rufus & Azrael <rufus-azrael@numericable.fr>
To: Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: [2.6.28-rc6-git1] compilation warnings and section mismatches
Date: Sun, 23 Nov 2008 10:40:39 +0100	[thread overview]
Message-ID: <49292517.5050200@numericable.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

Hi all,


Here are my warnings and section mismatches when compiling 
2.6.28-rc6-git1 kernel. All are fixed in git trees but patches are not 
yet pulled in mainline.

Regards.




[-- Attachment #2: 2.6.28-rc6-git1_compilation_warnings_section_mismatches --]
[-- Type: text/plain, Size: 2346 bytes --]

arch/x86/kernel/cpu/mtrr/main.c: In function ‘mtrr_cleanup’:
arch/x86/kernel/cpu/mtrr/main.c:1363: attention : ‘gran_factor’ may be used uninitialized in this function
arch/x86/kernel/cpu/mtrr/main.c:1364: attention : ‘gran_base’ may be used uninitialized in this function

fixed by patch in http://marc.info/?l=linux-kernel&m=122394648405506&w=2 but not yet in mainline
-----------------------------------------------------------------------------------------------------
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: 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.

fixed by patches in http://marc.info/?l=linux-kernel&m=122718681726939&w=2
and http://marc.info/?l=linux-kernel&m=122718656126513&w=2 but not yet in mainline
-----------------------------------------------------------------------------------------------------
WARNING: kernel/built-in.o(.text+0x10a50): 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+0x34230): 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.

fixed by patch in http://marc.info/?l=linux-kernel&m=122533953711446&w=2 but not yet in mainline
----------------------------------------------------------------------------------------------------

                 reply	other threads:[~2008-11-23  9:40 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=49292517.5050200@numericable.fr \
    --to=rufus-azrael@numericable.fr \
    --cc=linux-kernel@vger.kernel.org \
    --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