[PATCH 1/4] x86: coding style fixes in /arch/x86/pci/common.c

[Paolo Ciarrocchi]

Fix some coding style issues.


Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@xxxxxxxxx>
---
 arch/x86/pci/common.c |   12 +++++-------
 1 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c
index 52deabc..7388b1a 100644
--- a/arch/x86/pci/common.c
+++ b/arch/x86/pci/common.c
@@ -67,7 +67,7 @@ static void __devinit pcibios_fixup_ghosts(struct pci_bus *b)
 {
 	struct list_head *ln, *mn;
 	struct pci_dev *d, *e;
-	int mirror = PCI_DEVFN(16,0);
+	int mirror = PCI_DEVFN(16, 0);
 	int seen_host_bridge = 0;
 	int i;
 
@@ -76,14 +76,14 @@ static void __devinit pcibios_fixup_ghosts(struct pci_bus *b)
 		d = pci_dev_b(ln);
 		if ((d->class >> 8) == PCI_CLASS_BRIDGE_HOST)
 			seen_host_bridge++;
-		for (mn=ln->next; mn != &b->devices; mn=mn->next) {
+		for (mn = ln->next; mn != &b->devices; mn = mn->next) {
 			e = pci_dev_b(mn);
 			if (e->devfn != d->devfn + mirror ||
 			    e->vendor != d->vendor ||
 			    e->device != d->device ||
 			    e->class != d->class)
 				continue;
-			for(i=0; i<PCI_NUM_RESOURCES; i++)
+			for (i = 0; i < PCI_NUM_RESOURCES; i++)
 				if (e->resource[i].start != d->resource[i].start ||
 				    e->resource[i].end != d->resource[i].end ||
 				    e->resource[i].flags != d->resource[i].flags)
@@ -449,8 +449,7 @@ char * __devinit  pcibios_setup(char *str)
 	else if (!strcmp(str, "conf1")) {
 		pci_probe = PCI_PROBE_CONF1 | PCI_NO_CHECKS;
 		return NULL;
-	}
-	else if (!strcmp(str, "conf2")) {
+	} else if (!strcmp(str, "conf2")) {
 		pci_probe = PCI_PROBE_CONF2 | PCI_NO_CHECKS;
 		return NULL;
 	}
@@ -464,8 +463,7 @@ char * __devinit  pcibios_setup(char *str)
 	else if (!strcmp(str, "noacpi")) {
 		acpi_noirq_set();
 		return NULL;
-	}
-	else if (!strcmp(str, "noearly")) {
+	} else if (!strcmp(str, "noearly")) {
 		pci_probe |= PCI_PROBE_NOEARLY;
 		return NULL;
 	}
-- 
1.5.4.rc2.17.g257f

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/