mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Rose <johnrose@austin.ibm.com>
To: Greg KH <gregkh@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Hotplug List <pcihpd-discuss@lists.sourceforge.net>
Subject: struct pci_bus, no release() function?
Date: Mon, 02 Aug 2004 15:15:28 -0500	[thread overview]
Message-ID: <1091477728.23381.24.camel@sinatra.austin.ibm.com> (raw)

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.

Are architectures free to assign their own release function for
"devices" associated with struct pci_bus?  If so, does this have to
happen at boot, or can it happen right before the remove?

Thanks-
John


             reply	other threads:[~2004-08-03  5:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 20:15 John Rose [this message]
2004-08-09  6:45 ` [Pcihpd-discuss] " Greg KH
2004-08-09 16:34   ` John Rose
2004-08-10 16:30     ` Greg KH

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=1091477728.23381.24.camel@sinatra.austin.ibm.com \
    --to=johnrose@austin.ibm.com \
    --cc=gregkh@us.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
all inboxes | Powered by JetHome®