All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: greg@kroah.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: remove usage of pci_for_each_dev() in sound/oss/via82cxxx_audio.c
Date: Thu, 05 Jun 2003 00:18:50 -0400	[thread overview]
Message-ID: <3EDEC4AA.3050008@pobox.com> (raw)
In-Reply-To: <200306050328.h553SlEL011941@hera.kernel.org>

Linux Kernel Mailing List wrote:
> ChangeSet 1.1254.4.15, 2003/06/04 12:30:25-07:00, greg@kroah.com
> 
> 	[PATCH] PCI: remove usage of pci_for_each_dev() in sound/oss/via82cxxx_audio.c
> 
> 
> # This patch includes the following deltas:
> #	           ChangeSet	1.1254.4.14 -> 1.1254.4.15
> #	sound/oss/via82cxxx_audio.c	1.27    -> 1.28   
> #
> 
>  via82cxxx_audio.c |   11 +++++------
>  1 files changed, 5 insertions(+), 6 deletions(-)
> 
> 
> diff -Nru a/sound/oss/via82cxxx_audio.c b/sound/oss/via82cxxx_audio.c
> --- a/sound/oss/via82cxxx_audio.c	Wed Jun  4 20:28:51 2003
> +++ b/sound/oss/via82cxxx_audio.c	Wed Jun  4 20:28:51 2003
> @@ -1357,12 +1357,12 @@
>  {
>  	int minor = minor(inode->i_rdev);
>  	struct via_info *card;
> -	struct pci_dev *pdev;
> +	struct pci_dev *pdev = NULL;
>  	struct pci_driver *drvr;
>  
>  	DPRINTK ("ENTER\n");
>  
> -	pci_for_each_dev(pdev) {
> +	while ((pdev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, pdev)) != NULL) {
>  		drvr = pci_dev_driver (pdev);
>  		if (drvr == &via_driver) {
>  			assert (pci_get_drvdata (pdev) != NULL);


Looking at your various commits in this vein, it really looks like there 
needs to be a function that returns the PCI device, given the struct 
pci_driver pointer.  pci_find_driver() perhaps?

	Jeff




       reply	other threads:[~2003-06-05  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200306050328.h553SlEL011941@hera.kernel.org>
2003-06-05  4:18 ` Jeff Garzik [this message]
2003-06-05 21:16   ` [PATCH] PCI: remove usage of pci_for_each_dev() in sound/oss/via82cxxx_audio.c 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=3EDEC4AA.3050008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=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 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.