From: Sam Ravnborg <sam@ravnborg.org>
To: Alex Chiang <achiang@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [git pull] PCI changes for 2.6.30
Date: Wed, 1 Apr 2009 21:12:20 +0200 [thread overview]
Message-ID: <20090401191220.GB29673@uranus.ravnborg.org> (raw)
In-Reply-To: <20090401183749.GC8188@ldl.fc.hp.com>
On Wed, Apr 01, 2009 at 12:37:49PM -0600, Alex Chiang wrote:
> * Jesse Barnes <jbarnes@virtuousgeek.org>:
> > On Wed, 1 Apr 2009 10:01:12 -0700 (PDT)
> > Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > >
> > >
> > > On Tue, 31 Mar 2009, Jesse Barnes wrote:
> > > >
> > > > Please consider pulling my PCI tree from
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6
> > > > linux-next
> > >
> > > This produces
> > >
> > > WARNING: drivers/built-in.o(.text+0x69a1): Section mismatch in
> > > reference from the function dev_rescan_store() to the
> > > function .devinit.text:pci_rescan_bus() The function
> > > dev_rescan_store() references the function __devinit
> > > pci_rescan_bus(). This is often because dev_rescan_store lacks a
> > > __devinit annotation or the annotation of pci_rescan_bus is wrong.
> > >
> > > Hmm?
> >
> > Arg how did I miss that? Maybe the last build I did was missing
> > hotplug support or something... Anyway looking now (at first glance I
> > think pci_rescan_bus needs to drop __devinit).
>
> This was my fault. pci_rescan_bus() definitely does not want
> __devinit.
>
> But I'm confused -- didn't we used to have an option in
> menuconfig under Kernel Hacking that would turn on section
> mismatch warnings? I used to have that turned on, and don't
> remember turning it off, and I can't find it now.
>
> I'm told that we're supposed to set it on the make command line,
> like:
>
> make CONFIG_DEBUG_SECTION_MISMATCH=y -j16
>
> or something. Has this changed recently or am I just imagining
> things (or just plain stupid?)
That was maybe one year ago we had it in menuconfig.
When I get on top of things I will enable it and try to
help fixing the remaining warnings.
I have resisted enabling it for now as I cannot support the people
that see the warnings atm.
The patch to enable it is simple so if anyone want
to help fix the warnings then...
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 9638d99..ee5e6f3 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -95,10 +95,6 @@ config HEADERS_CHECK
config DEBUG_SECTION_MISMATCH
bool "Enable full Section mismatch analysis"
- depends on UNDEFINED
- # This option is on purpose disabled for now.
- # It will be enabled when we are down to a resonable number
- # of section mismatch warnings (< 10 for an allyesconfig build)
help
The section mismatch analysis checks if there are illegal
references from one section to another section.
Sam
next prev parent reply other threads:[~2009-04-01 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 19:13 Jesse Barnes
2009-04-01 17:01 ` Linus Torvalds
2009-04-01 17:13 ` Jesse Barnes
2009-04-01 18:37 ` Alex Chiang
2009-04-01 19:12 ` Sam Ravnborg [this message]
2009-04-01 22:23 ` Alex Chiang
2009-04-05 19:34 ` Sam Ravnborg
2009-04-06 15:19 ` Alex Chiang
2009-04-06 19:16 ` Sam Ravnborg
2009-04-02 0:24 ` Alex Chiang
2009-04-06 18:46 ` Jesse Barnes
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=20090401191220.GB29673@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=achiang@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.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®