Searched hist:"9 af15c38254d81c9991eba89335ca7c537d7f2c3" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/include/linux/ |
H A D | device.h | diff 9af15c38254d81c9991eba89335ca7c537d7f2c3 Wed Jan 18 07:04:39 CST 2017 Phil Sutter <phil@nwl.cc> device: Implement a bus agnostic dev_num_vf routine
Now that pci_bus_type has num_vf callback set, dev_num_vf can be implemented in a bus type independent way and the check for whether a PCI device is being handled in rtnetlink can be dropped.
Signed-off-by: Phil Sutter <phil@nwl.cc> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | pci.h | diff 9af15c38254d81c9991eba89335ca7c537d7f2c3 Wed Jan 18 07:04:39 CST 2017 Phil Sutter <phil@nwl.cc> device: Implement a bus agnostic dev_num_vf routine
Now that pci_bus_type has num_vf callback set, dev_num_vf can be implemented in a bus type independent way and the check for whether a PCI device is being handled in rtnetlink can be dropped.
Signed-off-by: Phil Sutter <phil@nwl.cc> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/net/core/ |
H A D | rtnetlink.c | diff 9af15c38254d81c9991eba89335ca7c537d7f2c3 Wed Jan 18 07:04:39 CST 2017 Phil Sutter <phil@nwl.cc> device: Implement a bus agnostic dev_num_vf routine
Now that pci_bus_type has num_vf callback set, dev_num_vf can be implemented in a bus type independent way and the check for whether a PCI device is being handled in rtnetlink can be dropped.
Signed-off-by: Phil Sutter <phil@nwl.cc> Signed-off-by: David S. Miller <davem@davemloft.net>
|