From: Chris Clayton <chris2553@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.24-rc3-git4 build warnings
Date: Thu, 29 Nov 2007 14:19:49 +0000 [thread overview]
Message-ID: <200711291419.49261.chris2553@googlemail.com> (raw)
Hi,
I've just built 2.6.24-rc3-git4 and got the following two warnings.
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0x90b6): Section mismatch: reference to
.init.text:cache_remove_shared_cpu_map (between 'free_cache_attributes' and
'show_level')
WARNING: vmlinux.o(.init.text+0x143bd): Section mismatch: reference to
.exit.text:cpufreq_stats_free_table (between 'cpufreq_stat_cpu_callback' and
'cpufreq_stats_init')
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
[...]
OBJCOPY arch/x86/boot/setup.bin
AS arch/x86/boot/compressed/head_32.o
CC arch/x86/boot/compressed/misc_32.o
include/asm/processor_32.h: In function `native_get_debugreg':
include/asm/processor_32.h:530: warning: asm operand 0 probably doesn't
match constraints
include/asm/processor_32.h: In function `native_set_debugreg':
include/asm/processor_32.h:557: warning: asm operand 0 probably doesn't
match constraints
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIP arch/x86/boot/compressed/vmlinux.bin.gz
Please cc me on any reply - I'm not subscribed.
Chris
--
Beer is proof that God loves us and wants us to be happy - Benjamin Franklin
next reply other threads:[~2007-11-29 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 14:19 Chris Clayton [this message]
2007-11-29 18:00 ` 2.6.24-rc3-git4 build warnings Adrian Bunk
2007-11-30 10:41 ` Chris Clayton
2007-12-01 19:36 ` Adrian Bunk
2007-12-01 19:49 ` Chris Clayton
2007-12-01 20:01 ` Adrian Bunk
2007-12-02 0:42 ` [2.6 patch] x86 intel_cacheinfo.c section fix Adrian Bunk
2007-12-04 12:56 ` Ingo Molnar
2007-12-02 0:43 ` [2.6 patch] drivers/cpufreq/cpufreq_stats.c " Adrian Bunk
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=200711291419.49261.chris2553@googlemail.com \
--to=chris2553@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.