Re: [PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases()

2012-07-09 Thread David Miller
From: Bjorn Helgaas Date: Mon, 09 Jul 2012 14:32:14 -0600 > The generic code to read P2P bridge windows is functionally equivalent > to the sparc-specific pci_cfg_fake_ranges(), so use the generic code. > > The "if (!res->start) res->start = ..." removed from the I/O window code > here was an

[PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases()

2012-07-09 Thread Bjorn Helgaas
The generic code to read P2P bridge windows is functionally equivalent to the sparc-specific pci_cfg_fake_ranges(), so use the generic code. The "if (!res->start) res->start = ..." removed from the I/O window code here was an artifact of the Intel 1K window support from 9d265124d051 and is no

[PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases()

2012-07-09 Thread Bjorn Helgaas
The generic code to read P2P bridge windows is functionally equivalent to the sparc-specific pci_cfg_fake_ranges(), so use the generic code. The if (!res-start) res-start = ... removed from the I/O window code here was an artifact of the Intel 1K window support from 9d265124d051 and is no longer

Re: [PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases()

2012-07-09 Thread David Miller
From: Bjorn Helgaas bhelg...@google.com Date: Mon, 09 Jul 2012 14:32:14 -0600 The generic code to read P2P bridge windows is functionally equivalent to the sparc-specific pci_cfg_fake_ranges(), so use the generic code. The if (!res-start) res-start = ... removed from the I/O window code