From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Removal of pci_find_* in 2.5
Date: Fri, 12 Jul 2002 17:36:01 -0700 [thread overview]
Message-ID: <20020713003601.GA12118@kroah.com> (raw)
Hi all,
Well, I've been trying to figure out a way to remove the existing
pci_find_device(), and other pci_find_* functions from the 2.5 kernel
without hurting to many things (well, things that people care about.)
Turns out these are very useful functions, outside of the "old" pci
framework, and I can't really justify removing them, so they are staying
for now (or until someone else can think of a replacement...)
The main reason for wanting to do this, is that any PCI driver that
relies on using pci_find_* to locate a device to control, will not work
with the existing PCI hotplug code. Moving forward, those drivers will
also not work with the driverfs, struct driver, or the device naming
code.
So if you own a PCI driver that does not conform to the "new" PCI api
(using pci_register_driver() and friends) consider yourself warned.
Your driver will NOT inherit any of the upcoming changes to the drivers
tree, which might cause them to break. Also remember, all of the people
that are buying hotplug PCI systems for their datacenters will not buy
your cards :)
thanks,
greg k-h
next reply other threads:[~2002-07-13 0:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 0:36 Greg KH [this message]
2002-07-13 2:23 ` Removal of pci_find_* in 2.5 Alan Cox
2002-07-13 1:12 ` David S. Miller
2002-07-13 14:46 ` Alan Cox
2002-07-13 20:52 ` David S. Miller
2002-07-13 13:45 ` Benjamin Herrenschmidt
2002-07-15 5:25 ` David S. Miller
2002-07-16 0:26 ` Greg KH
2002-07-14 20:07 ` Eric W. Biederman
2002-07-16 0:25 ` Greg KH
2002-07-16 10:56 ` Eric W. Biederman
2002-07-16 17:33 ` Patrick Mochel
2002-07-17 12:41 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 4:04 Matt_Domsch
2002-07-13 4:41 ` Jeff Garzik
2002-07-13 5:09 ` Greg KH
2002-07-13 14:35 ` Alan Cox
2002-07-13 15:37 ` Jeff Garzik
2002-07-13 17:06 ` Alan Cox
2002-07-13 19:28 ` Jeff Garzik
2002-07-13 19:33 ` Jeff Garzik
2002-07-13 13:13 Matt_Domsch
2002-07-16 19:23 Matt_Domsch
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=20020713003601.GA12118@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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