From ee26a5837c4a978ca4d0ae87ec12d117b97287aa Mon Sep 17 00:00:00 2001 From: Shingo Omura Date: Tue, 22 Jul 2025 10:10:40 +0900 Subject: [PATCH] Update staging/src/k8s.io/dynamic-resource-allocation/deviceattribute/pci_linux.go Co-authored-by: Kevin Klues --- .../dynamic-resource-allocation/deviceattribute/pci_linux.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/staging/src/k8s.io/dynamic-resource-allocation/deviceattribute/pci_linux.go b/staging/src/k8s.io/dynamic-resource-allocation/deviceattribute/pci_linux.go index 4d4bddd2611..3880e10d056 100644 --- a/staging/src/k8s.io/dynamic-resource-allocation/deviceattribute/pci_linux.go +++ b/staging/src/k8s.io/dynamic-resource-allocation/deviceattribute/pci_linux.go @@ -62,8 +62,8 @@ func GetPCIeRootAttributeByPCIBusID(pciBusID string) (DeviceAttribute, error) { // // ref: https://wiki.xenproject.org/wiki/Bus:Device.Function_(BDF)_Notation // -// /sys/devices has directory structure which reflects the hardware hierarchy in the system. -// Therefore, the device path may contains intermediate directories(devices). +// /sys/devices has a directory structure which reflects the hardware hierarchy in the system. +// Therefore, the device path may contain intermediate directories (devices). // Thus, we can not simply find the device path from the PCIAddress. // Fortunately, /sys/bus/pci/devices/
is a symlink to the actual device path in /sys/devices. // So we can resolve the actual device path by reading the symlink at /sys/bus/pci/devices/
.