| commit | 8b8d2b658f2cb7092672a56c72b41121ce786d93 | |
| author | Bjorn Helgaas <bhelgaas@google.com> | |
| Thu, 6 Jun 2013 18:10:46 +0000 (6 12:10 -0600) | ||
| committer | Bjorn Helgaas <bhelgaas@google.com> | |
| Thu, 6 Jun 2013 20:31:42 +0000 (6 14:31 -0600) | ||
| tree | 0e0d26115dcb96c4ee13436375ef783ff477234d | treesnapshot (tar.gz zip) |
| parent | f722406faae2d073cc1d01063d1123c35425939e | commitdiff |
PCI/AER: Don't parse HEST table for non-PCIe devices
AER is a PCIe-only capability, so there's no point in trying to match
a HEST PCIe structure with a non-PCIe device.
Previously, a HEST global AER bridge entry (type 8) could incorrectly
match *any* bridge, even a legacy PCI-PCI bridge, and a non-global
HEST entry could match a legacy PCI device.
Tested-by: Betty Dall <betty.dall@hp.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
AER is a PCIe-only capability, so there's no point in trying to match
a HEST PCIe structure with a non-PCIe device.
Previously, a HEST global AER bridge entry (type 8) could incorrectly
match *any* bridge, even a legacy PCI-PCI bridge, and a non-global
HEST entry could match a legacy PCI device.
Tested-by: Betty Dall <betty.dall@hp.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
| drivers/pci/pcie/aer/aerdrv_acpi.c | diffblobblamehistory |