From: maximilian attems <janitor@sternwelten.at>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com
Subject: [patch-kj] use list_for_each() drivers/pci/setup-bus.c
Date: Fri, 23 Jul 2004 11:21:53 +0200 [thread overview]
Message-ID: <20040723092153.GD14000@stro.at> (raw)
Use list_for_each() where applicable
- for (list = ymf_devs.next; list != &ymf_devs; list = list->next) {
+ list_for_each(list, &ymf_devs) {
pure cosmetic change, defined as a preprocessor macro in:
include/linux/list.h
patch against 2.6.7-bk20, please tell if you need against newer.
From: Domen Puncer <domen@coderock.org>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
---
linux-2.6.7-bk20-max/drivers/pci/setup-bus.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff -puN drivers/pci/setup-bus.c~list_for_each-pci-setup-bus drivers/pci/setup-bus.c
--- linux-2.6.7-bk20/drivers/pci/setup-bus.c~list_for_each-pci-setup-bus 2004-07-11 14:41:20.000000000 +0200
+++ linux-2.6.7-bk20-max/drivers/pci/setup-bus.c 2004-07-11 14:41:20.000000000 +0200
@@ -537,10 +537,11 @@ pci_assign_unassigned_resources(void)
/* Depth first, calculate sizes and alignments of all
subordinate buses. */
- for(ln=pci_root_buses.next; ln != &pci_root_buses; ln=ln->next)
+ list_for_each(ln, &pci_root_buses) {
pci_bus_size_bridges(pci_bus_b(ln));
+ }
/* Depth last, allocate resources and update the hardware. */
- for(ln=pci_root_buses.next; ln != &pci_root_buses; ln=ln->next) {
+ list_for_each(ln, &pci_root_buses) {
pci_bus_assign_resources(pci_bus_b(ln));
pci_enable_bridges(pci_bus_b(ln));
}
next reply other threads:[~2004-07-23 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 9:21 maximilian attems [this message]
2004-08-02 22:42 ` [patch-kj] use list_for_each() drivers/pci/setup-bus.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=20040723092153.GD14000@stro.at \
--to=janitor@sternwelten.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox