From: Thierry Reding <thierry.reding@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] PCI: Use device_match_always()
Date: Mon, 6 Jun 2016 09:32:37 +0200 [thread overview]
Message-ID: <20160606073238.1073-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20160606073238.1073-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
There is now a common implementation for a match function that will
always match, so the PCI-specific implementation can be removed.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/pci/probe.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 8e3ef720997d..3db06d8d6497 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -62,11 +62,6 @@ static struct resource *get_pci_domain_busn_res(int domain_nr)
return &r->res;
}
-static int find_anything(struct device *dev, void *data)
-{
- return 1;
-}
-
/*
* Some device drivers need know if pci is initiated.
* Basically, we think pci is not initiated when there
@@ -77,7 +72,7 @@ int no_pci_devices(void)
struct device *dev;
int no_devices;
- dev = bus_find_device(&pci_bus_type, NULL, NULL, find_anything);
+ dev = bus_find_device(&pci_bus_type, NULL, NULL, device_match_always);
no_devices = (dev == NULL);
put_device(dev);
return no_devices;
--
2.8.3
next prev parent reply other threads:[~2016-06-06 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 7:32 [PATCH 1/3] driver-core: Implement device_match_always() Thierry Reding
2016-06-06 7:32 ` Thierry Reding [this message]
2016-06-10 16:13 ` [PATCH 2/3] PCI: Use device_match_always() Bjorn Helgaas
2016-06-10 16:33 ` Thierry Reding
2016-06-06 7:32 ` [PATCH 3/3] scsi: " Thierry Reding
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=20160606073238.1073-2-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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