From: Greg KH <greg@kroah.com>
To: Scott Murray <scottm@somanetworks.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] Make hot unplugging of PCI buses work
Date: Sun, 23 Feb 2003 22:08:10 -0800 [thread overview]
Message-ID: <20030224060810.GB31528@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302231531450.2559-100000@rancor.yyz.somanetworks.com>
On Sun, Feb 23, 2003 at 04:01:10PM -0500, Scott Murray wrote:
> 1) The description of pci_remove_bus_device says "informing the drivers
> that the device has been removed", yet unless I'm missing some sysfs
> wrinkle, no call will be made to an attached driver's remove callback.
It gets called after device_unregister() is called on the pci device,
through the driver core, and is actually done in the pci_device_remove()
function in driver/pci/pci-driver.c
Hm, I just realized that the pci hotplug drivers were calling the remove
function twice (once on their own, and then through sysfs), this patch
will fix that.
> > Can't you just fix up the current users to use "pci_remove_bus_device()".
> > The breakage seems a bit spiteful ;)
>
> The current device removal code in all of the PCI hotplug drivers are
> based to varying degrees on sets of callbacks driven by the pci_visit_*
> family of functions, and will hence need varying amounts of rework to be
> able to just call pci_remove_bus_device instead. My cPCI hotplug driver
> and the ACPI based driver are likely the easiest to change over, since
> they attempt none of the more sophisticated resource management tricks
> that the Compaq and IBM drivers do.
It shouldn't be that tough to convert the Compaq and IBM drivers, I'll
work on it tonight and test on hardware tomorrow.
thanks,
greg k-h
next prev parent reply other threads:[~2003-02-24 6:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 17:34 [PATCH] Make hot unplugging of PCI buses work Russell King
2003-02-23 18:16 ` Jeff Garzik
2003-02-23 18:57 ` Linus Torvalds
2003-02-23 19:32 ` Russell King
2003-02-23 21:29 ` Alan Cox
2003-02-24 0:10 ` Ivan Kokshaysky
2003-02-23 21:01 ` Scott Murray
2003-02-23 21:24 ` Russell King
2003-02-23 22:27 ` Scott Murray
2003-02-24 0:59 ` Linus Torvalds
2003-02-24 5:40 ` Scott Murray
2003-02-24 6:08 ` Greg KH [this message]
2003-02-24 5:48 ` Greg KH
2003-02-24 10:03 ` Russell King
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=20030224060810.GB31528@kroah.com \
--to=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=scottm@somanetworks.com \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.