From: "Davide Pesavento" <davidepesa@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.26-rc1 - section mismatches on x86
Date: Sun, 4 May 2008 21:41:33 +0200 [thread overview]
Message-ID: <2da21fe50805041241k4b79ef87j689cbe9d93d6d1d4@mail.gmail.com> (raw)
2008/4/11 Sam Ravnborg <sam@ravnborg.org>:
> On Fri, Apr 11, 2008 at 08:02:06PM +0200, Davide Pesavento wrote:
> > While compiling linux-2.6.25-rc8-git7 with
> > CONFIG_DEBUG_SECTION_MISMATCH=y, I noticed the following "section
> > mismatch" warnings.
>
> Thanks for your report Davide.
> We have several "Section mismatch warning" fixes queued
> up in -mm and in x86.git so I expect most of the ones below
> to be already fixed.
> Merging is postponed until next merge window.
>
> A similar report at -rc1 time would be good.
>
> Sam
>
Hello again!
I tried 2.6.26-rc1 and only these two warnings are left:
WARNING: vmlinux.o(.text+0x10fe7): Section mismatch in reference from
the function cpu_exit_clear() to the function
.cpuinit.text:cpu_uninit()
The function cpu_exit_clear() references
the function __cpuinit cpu_uninit().
This is often because cpu_exit_clear lacks a __cpuinit
annotation or the annotation of cpu_uninit is wrong.
WARNING: vmlinux.o(.text+0x1e26e4): Section mismatch in reference from
the function pci_scan_bus_on_node() to the function
.devinit.text:pci_scan_bus_parented()
The function pci_scan_bus_on_node() references
the function __devinit pci_scan_bus_parented().
This is often because pci_scan_bus_on_node lacks a __devinit
annotation or the annotation of pci_scan_bus_parented is wrong.
reply other threads:[~2008-05-04 19:41 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=2da21fe50805041241k4b79ef87j689cbe9d93d6d1d4@mail.gmail.com \
--to=davidepesa@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
all inboxes | Powered by JetHome®