Linux-Next discussions
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Alex Chiang <achiang@hp.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	a.beregalov@gmail.com, lenb@kernel.org
Subject: Re: linux-next: Tree for June 17 (pci/slot)
Date: Thu, 18 Jun 2009 14:04:18 -0700	[thread overview]
Message-ID: <20090618140418.2e078701@jbarnes-g45> (raw)
In-Reply-To: <20090618010357.GC29472@ldl.fc.hp.com>

On Wed, 17 Jun 2009 19:03:57 -0600
Alex Chiang <achiang@hp.com> wrote:

> * Alex Chiang <achiang@hp.com>:
> > diff --git a/drivers/pci/Makefile b/drivers/pci/Makefile
> > index ba6af16..0be4efd 100644
> > --- a/drivers/pci/Makefile
> > +++ b/drivers/pci/Makefile
> > @@ -2,10 +2,11 @@
> >  # Makefile for the PCI bus specific drivers.
> >  #
> >  
> > -obj-y		+= access.o bus.o probe.o remove.o pci.o
> > quirks.o slot.o \
> > -			pci-driver.o search.o pci-sysfs.o rom.o
> > setup-res.o \ +obj-y		+= access.o bus.o probe.o
> > remove.o pci.o quirks.o \
> > +			pci-driver.o search.o rom.o setup-res.o \
> >  			irq.o
> >  obj-$(CONFIG_PROC_FS) += proc.o
> > +obj-$(CONFIG_SYSFS) += slot.o pci-sysfs.o
> 
> Sigh, this won't work because the PCI core blithely assumes we have
> sysfs:
> 
> drivers/built-in.o: In function `pci_bus_add_device':
> /kio/work/achiang/kernels/linux-2.6/drivers/pci/bus.c:89: undefined
> reference to `pci_create_sysfs_dev_files' drivers/built-in.o: In
> function
> `pci_stop_dev': /kio/work/achiang/kernels/linux-2.6/drivers/pci/remove.c:24:
> undefined reference to `pci_remove_sysfs_dev_files'
> 
> So, here is v3 that actually does build with !CONFIG_SYSFS. It
> touches a bit more now, but I believe it is still appropriate
> because neither pci_slot.ko nor any of the drivers in
> drivers/pci/hotplug/ are useful without sysfs.
> 
> From: Alex Chiang <achiang@hp.com>
> 
> PCI: drivers/pci/slot.c should depend on CONFIG_SYSFS
> 
> There is no way to interact with a physical PCI slot without
> sysfs, so encode the dependency and prevent this build error:
> 
> 	drivers/pci/slot.c: In function 'pci_hp_create_module_link':
> 	drivers/pci/slot.c:327: error: 'module_kset' undeclared
> 
> This patch _should_ make pci-sysfs.o depend on CONFIG_SYSFS too,
> but we cannot (yet) because the PCI core merrily assumes the
> existence of sysfs:
> 
> 	drivers/built-in.o: In function `pci_bus_add_device':
> 	drivers/pci/bus.c:89: undefined reference to
> `pci_create_sysfs_dev_files' drivers/built-in.o: In function
> `pci_stop_dev': drivers/pci/remove.c:24: undefined reference to
> `pci_remove_sysfs_dev_files'
> 
> So do the minimal bit for now and figure out how to untangle it
> later.

Applied, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2009-06-18 21:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  5:53 linux-next: Tree for June 17 Stephen Rothwell
2009-06-17 16:26 ` linux-next: Tree for June 17 (pci/slot) Randy Dunlap
2009-06-17 16:36   ` Matthew Wilcox
2009-06-17 17:29     ` Jesse Barnes
2009-06-17 17:43       ` Randy Dunlap
2009-06-17 23:10         ` Jesse Barnes
2009-06-18  0:38           ` Alex Chiang
2009-06-18  0:46             ` Alex Chiang
2009-06-18  0:58               ` Randy Dunlap
2009-06-18  1:03               ` Alex Chiang
2009-06-18 15:14                 ` Randy Dunlap
2009-06-18 21:04                 ` Jesse Barnes [this message]

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=20090618140418.2e078701@jbarnes-g45 \
    --to=jesse.barnes@intel.com \
    --cc=a.beregalov@gmail.com \
    --cc=achiang@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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