Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933114AbZDAWXZ (ORCPT ); Wed, 1 Apr 2009 18:23:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755707AbZDAWXN (ORCPT ); Wed, 1 Apr 2009 18:23:13 -0400 Received: from g4t0017.houston.hp.com ([15.201.24.20]:37612 "EHLO g4t0017.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753804AbZDAWXM (ORCPT ); Wed, 1 Apr 2009 18:23:12 -0400 Date: Wed, 1 Apr 2009 16:23:10 -0600 From: Alex Chiang To: Sam Ravnborg Cc: Jesse Barnes , Linus Torvalds , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [git pull] PCI changes for 2.6.30 Message-ID: <20090401222310.GA31290@ldl.fc.hp.com> References: <20090331121331.3673cf59@hobbes> <20090401101309.67d0bea5@hobbes> <20090401183749.GC8188@ldl.fc.hp.com> <20090401191220.GB29673@uranus.ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090401191220.GB29673@uranus.ravnborg.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3158 Lines: 86 * Sam Ravnborg : > On Wed, Apr 01, 2009 at 12:37:49PM -0600, Alex Chiang wrote: > > * Jesse Barnes : > > > On Wed, 1 Apr 2009 10:01:12 -0700 (PDT) > > > Linus Torvalds 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. Ah, ok. > I have resisted enabling it for now as I cannot support the people > that see the warnings atm. Nod, makes sense. I took a look at the warning that Linus mentioned, and I'm not entirely sure how to fix it. The problem is this: http://git.kernel.org/?p=linux/kernel/git/jbarnes/pci-2.6.git;a=commit;h=3ed4fd96b3188406ac5357d9290bcffa08c65cf6 I initially annoted pci_rescan_bus as __devinit, which it shouldn't have. Removing the annotation though, produces these other warnings: WARNING: vmlinux.o(.text+0x1b9be6): Section mismatch in reference from the function pci_rescan_bus() to the function .devinit.text:pci_scan_child_bus() The function pci_rescan_bus() references the function __devinit pci_scan_child_bus(). This is often because pci_rescan_bus lacks a __devinit annotation or the annotation of pci_scan_child_bus is wrong. Reading through Documentation/PCI/pci.txt says that under CONFIG_HOTPLUG, __devinit should be a nop? I do have this in my .config: CONFIG_HOTPLUG=y So I'm not sure what I'm doing wrong? Thanks. /ac -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/