From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Yet more PCI fixes for 2.5.70
Date: Tue, 10 Jun 2003 11:49:27 -0700 [thread overview]
Message-ID: <1055270967899@kroah.com> (raw)
In-Reply-To: <10552709671915@kroah.com>
ChangeSet 1.1345, 2003/06/09 15:52:51-07:00, greg@kroah.com
PCI: remove pci_present() from drivers/net/wan/lmc/lmc_main.c
drivers/net/wan/lmc/lmc_main.c | 8 --------
drivers/net/wan/lmc/lmc_ver.h | 2 --
2 files changed, 10 deletions(-)
diff -Nru a/drivers/net/wan/lmc/lmc_main.c b/drivers/net/wan/lmc/lmc_main.c
--- a/drivers/net/wan/lmc/lmc_main.c Tue Jun 10 11:20:20 2003
+++ b/drivers/net/wan/lmc/lmc_main.c Tue Jun 10 11:20:20 2003
@@ -1034,14 +1034,6 @@
u8 intcf = 0;
struct pci_dev *pdev = NULL;
- /* The card is only available on PCI, so if we don't have a
- * PCI bus, we are in trouble.
- */
-
- if (!pci_present()) {
-/* printk ("%s: We really want a pci bios!\n", dev->name);*/
- return -1;
- }
/* Loop basically until we don't find anymore. */
while ((pdev = pci_find_class (PCI_CLASS_NETWORK_ETHERNET << 8, pdev))) {
if (pci_enable_device(pdev))
diff -Nru a/drivers/net/wan/lmc/lmc_ver.h b/drivers/net/wan/lmc/lmc_ver.h
--- a/drivers/net/wan/lmc/lmc_ver.h Tue Jun 10 11:20:20 2003
+++ b/drivers/net/wan/lmc/lmc_ver.h Tue Jun 10 11:20:20 2003
@@ -69,12 +69,10 @@
#if LINUX_VERSION_CODE < 0x20155 /* basically 2.2 plus */
#define LMC_DEV_KFREE_SKB(skb) dev_kfree_skb((skb), FREE_WRITE)
-#define LMC_PCI_PRESENT() pcibios_present()
#else /* Mostly 2.0 kernels */
#define LMC_DEV_KFREE_SKB(skb) dev_kfree_skb(skb)
-#define LMC_PCI_PRESENT() pci_present()
#endif
next prev parent reply other threads:[~2003-06-10 18:48 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 18:49 [PATCH] Yet more PCI fixes for 2.5.70 Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH [this message]
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 18:33 [BK PATCH] " Greg KH
2003-06-10 18:49 ` [PATCH] " Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` Greg KH
2003-06-10 18:49 ` 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=1055270967899@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