public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: John Rose <johnrose@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Hotplug List <pcihpd-discuss@lists.sourceforge.net>
Subject: Re: [Pcihpd-discuss] struct pci_bus, no release() function?
Date: Tue, 10 Aug 2004 09:30:29 -0700	[thread overview]
Message-ID: <20040810163029.GA30942@kroah.com> (raw)
In-Reply-To: <1092069286.20704.20.camel@sinatra.austin.ibm.com>

On Mon, Aug 09, 2004 at 11:34:46AM -0500, John Rose wrote:
> On Mon, 2004-08-09 at 01:45, Greg KH wrote:
> > On Mon, Aug 02, 2004 at 03:15:28PM -0500, John Rose wrote:
> > > At probe time, pci_scan_bus_parented() allocates and registers a struct
> > > device for each PCI bus it scans.  This generic device structure never
> > > gets assigned a "release" function.  
> > > 
> > > Attempts to unregister such a PCI Bus at runtime result in a kernel
> > > message like:
> > > Device 'pci0001:00' does not have a release() function, it is broken and
> > > must be fixed.
> > 
> > You're right, that should be fixed.  Care to send a patch?  Should just
> > be a 1 line change.  You can tell no one else has tried to remove a root
> > bus device before...
> > 
> > > Are architectures free to assign their own release function for
> > > "devices" associated with struct pci_bus?
> > 
> > Why would they want to?  It should just be set to pci_release_dev, like
> > all other struct pci_dev devices are, right?
> 
> Root buses don't have an associated pci_dev struct, so this function
> won't do.

Ah, good point.  We should probably fix that up and make it a struct
pci_dev.  Or just make a release function for the struct device we
create.  Either way is fine for me.

thanks,

greg k-h

      reply	other threads:[~2004-08-10 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 20:15 struct pci_bus, no release() function? John Rose
2004-08-09  6:45 ` [Pcihpd-discuss] " Greg KH
2004-08-09 16:34   ` John Rose
2004-08-10 16:30     ` Greg KH [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=20040810163029.GA30942@kroah.com \
    --to=greg@kroah.com \
    --cc=johnrose@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    /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