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: <1055270967446@kroah.com> (raw)
In-Reply-To: <10552709672859@kroah.com>
ChangeSet 1.1348, 2003/06/09 15:54:51-07:00, greg@kroah.com
PCI: remove pci_present() from drivers/pci/proc.c
drivers/pci/proc.c | 22 ++++++++++------------
1 files changed, 10 insertions(+), 12 deletions(-)
diff -Nru a/drivers/pci/proc.c b/drivers/pci/proc.c
--- a/drivers/pci/proc.c Tue Jun 10 11:20:02 2003
+++ b/drivers/pci/proc.c Tue Jun 10 11:20:02 2003
@@ -579,19 +579,17 @@
static int __init pci_proc_init(void)
{
- if (pci_present()) {
- struct proc_dir_entry *entry;
- struct pci_dev *dev = NULL;
- proc_bus_pci_dir = proc_mkdir("pci", proc_bus);
- entry = create_proc_entry("devices", 0, proc_bus_pci_dir);
- if (entry)
- entry->proc_fops = &proc_bus_pci_dev_operations;
- proc_initialized = 1;
- while ((dev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
- pci_proc_attach_device(dev);
- }
- legacy_proc_init();
+ struct proc_dir_entry *entry;
+ struct pci_dev *dev = NULL;
+ proc_bus_pci_dir = proc_mkdir("pci", proc_bus);
+ entry = create_proc_entry("devices", 0, proc_bus_pci_dir);
+ if (entry)
+ entry->proc_fops = &proc_bus_pci_dev_operations;
+ proc_initialized = 1;
+ while ((dev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
+ pci_proc_attach_device(dev);
}
+ legacy_proc_init();
return 0;
}
next prev parent reply other threads:[~2003-06-10 18:36 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
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
-- 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=1055270967446@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