On 6/7/2017 5:11 PM, Jan Blunck wrote: > On Tue, Jun 6, 2017 at 5:10 PM, Ferruh Yigit <[email protected]> wrote: >> rte_driver->name has the driver name and all physical and virtual >> devices has access to it. >> >> Previously it was not possible for virtual ethernet devices to access >> rte_driver->name field (because eth_dev used to keep only pci_dev), >> and it was required to save driver name in the device private struct. >> >> After re-works on bus and vdev, it is possible for all bus types to >> access rte_driver. >> >> It is able to remove the driver name from ethdev device private data and >> use eth_dev->device->driver->name. >> >> Signed-off-by: Ferruh Yigit <[email protected]> >> --- >> Cc: Gaetan Rivet <[email protected]> >> Cc: Jan Blunck <[email protected]> >> >> v2: >> * rebase on latest next-net > > Acked-by: Jan Blunck <[email protected]>
Applied to dpdk-next-net/master, thanks.
