summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/kvm
diff options
context:
space:
mode:
authorXiongfeng Wang <wangxiongfeng2@huawei.com>2023-08-04 15:56:30 +0800
committerMichael Ellerman <mpe@ellerman.id.au>2023-08-16 23:54:48 +1000
commit0e1cd3d9f82eb5440d32d4c0f12c65403b956cb5 (patch)
tree53d4df86c95f8537345a005ee8d042ecec5231ef /arch/powerpc/kvm
parent6039fcd3fba99451ea9d013c4d3a65a40b2feff0 (diff)
downloadlinux-0e1cd3d9f82eb5440d32d4c0f12c65403b956cb5.tar.gz
linux-0e1cd3d9f82eb5440d32d4c0f12c65403b956cb5.tar.bz2
linux-0e1cd3d9f82eb5440d32d4c0f12c65403b956cb5.zip
cxl: Use pci_find_vsec_capability() to simplify the code
PCI core add pci_find_vsec_capability() to query VSEC. We can use that core API to simplify the code. The only logical change is that pci_find_vsec_capability check the Vendor ID before finding the VSEC. PCI spec rev 5.0 says in 7.9.5.2 Vendor-Specific Header: VSEC ID - This field is a vendor-defined ID number that indicates the nature and format of the VSEC structure Software must qualify the Vendor ID before interpreting this field. Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com> Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://msgid.link/20230804075630.186054-1-wangxiongfeng2@huawei.com
Diffstat (limited to 'arch/powerpc/kvm')
0 files changed, 0 insertions, 0 deletions