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:30 -0700 [thread overview]
Message-ID: <10552709703999@kroah.com> (raw)
In-Reply-To: <10552709702206@kroah.com>
ChangeSet 1.1389, 2003/06/10 10:32:40-07:00, greg@kroah.com
[PATCH] PCI: remove pci_for_each_bus() macro as there are now no more users of it.
include/linux/pci.h | 3 ---
1 files changed, 3 deletions(-)
diff -Nru a/include/linux/pci.h b/include/linux/pci.h
--- a/include/linux/pci.h Tue Jun 10 11:15:28 2003
+++ b/include/linux/pci.h Tue Jun 10 11:15:28 2003
@@ -525,9 +525,6 @@
extern struct list_head pci_root_buses; /* list of all known PCI buses */
extern struct list_head pci_devices; /* list of all devices */
-#define pci_for_each_bus(bus) \
- for(bus = pci_bus_b(pci_root_buses.next); bus != pci_bus_b(&pci_root_buses); bus = pci_bus_b(bus->node.next))
-
int pci_present(void);
void pcibios_fixup_bus(struct pci_bus *);
int pcibios_enable_device(struct pci_dev *, int mask);
next prev parent reply other threads:[~2003-06-10 21:14 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
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 [this message]
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=10552709703999@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 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.