The patch titled
increment pos before looking for the next cap in __pci_find_next_ht_cap
has been removed from the -mm tree. Its filename was
increment-pos-before-looking-for-the-next-cap-in-__pci_find_next_ht_cap.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: increment pos before looking for the next cap in __pci_find_next_ht_cap
From: Brice Goglin <brice@xxxxxxxx>
While testing 2.6.20-rc3 on a machine with some CK804 chipsets, we noticed
that quirk_nvidia_ck804_msi_ht_cap() was not detecting HT MSI capabilities
anymore. It is actually caused by the MSI mapping on the root chipset
being the 2nd HT capability in the chain. pci_find_ht_capability() does
not seem to find anything but the first HT cap correctly, because it
forgets to increment the position before looking for the next cap. The
following patch seems to fix it.
At least, this proves that having a ttl is good idea since the machine
would have been stucked in an infinite loop if we didn't have a ttl :)
We have to pass pos + PCI_CAP_LIST_NEXT to __pci_find_next_cap_ttl to
get the next HT cap instead of the same one again.
Signed-off-by: Brice Goglin <brice@xxxxxxxx>
Signed-off-by: Andrew J. Gallatin <gallatin@xxxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/pci/pci.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/pci/pci.c~increment-pos-before-looking-for-the-next-cap-in-__pci_find_next_ht_cap drivers/pci/pci.c
--- a/drivers/pci/pci.c~increment-pos-before-looking-for-the-next-cap-in-__pci_find_next_ht_cap
+++ a/drivers/pci/pci.c
@@ -254,7 +254,8 @@ static int __pci_find_next_ht_cap(struct
if ((cap & mask) == ht_cap)
return pos;
- pos = __pci_find_next_cap_ttl(dev->bus, dev->devfn, pos,
+ pos = __pci_find_next_cap_ttl(dev->bus, dev->devfn,
+ pos + PCI_CAP_LIST_NEXT,
PCI_CAP_ID_HT, &ttl);
}
_
Patches currently in -mm which might be from brice@xxxxxxxx are
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
