All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc3-git4 build warnings
Date: Sat, 1 Dec 2007 20:36:36 +0100	[thread overview]
Message-ID: <20071201193636.GC15974@stusta.de> (raw)
In-Reply-To: <200711291419.49261.chris2553@googlemail.com>

On Thu, Nov 29, 2007 at 02:19:49PM +0000, Chris Clayton wrote:
> 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')
>...

You seem to be using gcc 3.3 or 3.4.

I'll send patches for these.

> Chris

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2007-12-01 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 14:19 2.6.24-rc3-git4 build warnings Chris Clayton
2007-11-29 18:00 ` Adrian Bunk
2007-11-30 10:41   ` Chris Clayton
2007-12-01 19:36 ` Adrian Bunk [this message]
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=20071201193636.GC15974@stusta.de \
    --to=bunk@kernel.org \
    --cc=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.