diff options
author | Naveen Naidu <naveennaidu479@gmail.com> | 2021-11-18 19:33:29 +0530 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2021-11-18 14:13:18 -0600 |
commit | 0242132da26a928801cbb6ab96daf77e7815e084 (patch) | |
tree | 6e4b95b7e795cd926ea3a69c9a53affd87a61546 /Documentation/COPYING-logo | |
parent | a3b0f10db148f57591bd4559f01246a06a6a7e72 (diff) | |
download | linux-0242132da26a928801cbb6ab96daf77e7815e084.tar.bz2 |
PCI/DPC: Use PCI_POSSIBLE_ERROR() to check config reads
When config pci_ops.read() can detect failed PCI transactions, the data
returned to the CPU is PCI_ERROR_RESPONSE (~0 or 0xffffffff).
Obviously a successful PCI config read may *also* return that data if a
config register happens to contain ~0, so it doesn't definitively indicate
an error unless we know the register cannot contain ~0.
Use PCI_POSSIBLE_ERROR() to check the response we get when we read data
from hardware. This unifies PCI error response checking and makes error
checks consistent and easier to find.
Compile tested only.
Link: https://lore.kernel.org/r/9b0632f1f183432149f495cf12bdd5a72cc597a4.1637243717.git.naveennaidu479@gmail.com
Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'Documentation/COPYING-logo')
0 files changed, 0 insertions, 0 deletions