From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] updating obsolete pci_find_* routines
Date: Sun, 28 Jan 2007 01:40:01 +0000 [thread overview]
Message-ID: <20070128014001.GC2902@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701271925420.3864@CPE00045a9c397f-CM001225dbafb6>
On 27.01.2007 [19:27:56 -0500], Robert P. J. Day wrote:
>
> From Documentation/pci.txt:
>
> 9. Obsolete functions
> ~~~~~~~~~~~~~~~~~~~~~
>
> There are several functions which you might come across when trying to
> port an old driver to the new PCI interface. They are no longer
> present in the kernel as they aren't compatible with hotplug or PCI
> domains or having sane locking.
>
> pci_find_device() Superseded by pci_get_device()
> pci_find_subsys() Superseded by pci_get_subsys()
> pci_find_slot() Superseded by pci_get_slot()
>
> so these three changes would be simple text substitutions of the
> routine names, would they? the args have the same semantics and
> everything? just curious.
No, see the kernel-janitor archives.
Among other things, many drivers that still use pci_find_device()
probably should be reworked to use struct pci_driver semantics.
And pci_get_device() requires a pci_dev_put() when the driver is done
with the struct pci_dev.
Thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-01-28 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 0:27 [KJ] updating obsolete pci_find_* routines Robert P. J. Day
2007-01-28 1:40 ` Nishanth Aravamudan [this message]
2007-01-28 7:17 ` Robert P. J. Day
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=20070128014001.GC2902@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@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 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.