From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] pcibios_* removals for 2.5.40
Date: Fri, 04 Oct 2002 14:03:45 -0400 [thread overview]
Message-ID: <3D9DD801.4090603@pobox.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210040930581.1723-100000@home.transmeta.com
Linus Torvalds wrote:
> On Thu, 3 Oct 2002, Greg KH wrote:
>
>>Here's some changesets that remove the pcibios_find_class(),
>>pci_find_device(), and pcibios_present() functions. These functions
>>have been marked as obsolete since the 2.2 kernel, so it's about time
>>that we removed them.
>
>
> They are still in use by a lot of drivers.. I hate to break even more
> drivers at this point in 2.5.x, and so quite frankly I'd rather just do
> this in early 2.7.x instead. Unless somebody really steps up to the plate
> and also fixes the drivers ("it's a ton of fun, and imagine all the
> adoration you'll get from teenage girls/boys/ninja turtles for doing it")
Removing pcibios_present() makes a lot of sense, I have considered it
deprecated for quite a while now.
Further (more a note to Greg), often the pci[bios]_present() call can be
removed completely: when it is followed by a pci_find_xxx or
pci_register_driver() probe, which will obviously not find anything if
PCI bus is absent, the pci_present() call can be removed completely.
I would love to deprecate pcibios_{read,write}_foo but I don't think we
can remove them yet. Likewise for pcibios_find_xxx... I haven't look at
all the examples, but I would be worried about breaking ancient (but
working) code.
That said, if you wanna do the cleanup, I wouldn't object to removing
pcibios_find_xxx...
Jeff
prev parent reply other threads:[~2002-10-04 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 22:40 [BK PATCH] pcibios_* removals for 2.5.40 Greg KH
2002-10-03 22:40 ` Greg KH
2002-10-03 22:41 ` Greg KH
2002-10-03 22:41 ` Greg KH
2002-10-04 16:33 ` Linus Torvalds
2002-10-04 16:53 ` Alan Cox
2002-10-04 17:30 ` Linus Torvalds
2002-10-04 18:01 ` Greg KH
2002-10-04 16:59 ` Greg KH
2002-10-04 17:28 ` Alan Cox
2002-10-04 18:07 ` Arnaldo Carvalho de Melo
2002-10-04 20:51 ` Greg KH
2002-10-04 20:52 ` Greg KH
2002-10-04 20:53 ` Greg KH
2002-10-04 20:54 ` Greg KH
2002-10-04 21:34 ` Jeff Garzik
2002-10-04 21:52 ` Greg KH
2002-10-04 21:36 ` Jeff Garzik
2002-10-04 21:40 ` Jeff Garzik
2002-10-04 21:53 ` Greg KH
2002-10-04 22:14 ` Russell King
2002-10-04 18:03 ` Jeff Garzik [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=3D9DD801.4090603@pobox.com \
--to=jgarzik@pobox.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox