Re: [dpdk-dev] [PATCH v2] bus/pci: use device driver name instead of handler type

2018-10-28 Thread Thomas Monjalon
26/10/2018 16:03, Burakov, Anatoly: > On 25-Oct-18 11:49 AM, Alejandro Lucero wrote: > > Invoking the right pci read/write functions is based on interrupt > > handler type. However, this is not configured for secondary processes > > precluding to use those functions. > > > > This patch fixes the i

Re: [dpdk-dev] [PATCH v2] bus/pci: use device driver name instead of handler type

2018-10-26 Thread Burakov, Anatoly
On 25-Oct-18 11:49 AM, Alejandro Lucero wrote: Invoking the right pci read/write functions is based on interrupt handler type. However, this is not configured for secondary processes precluding to use those functions. This patch fixes the issue using the driver name the device is bound to instea

[dpdk-dev] [PATCH v2] bus/pci: use device driver name instead of handler type

2018-10-25 Thread Alejandro Lucero
Invoking the right pci read/write functions is based on interrupt handler type. However, this is not configured for secondary processes precluding to use those functions. This patch fixes the issue using the driver name the device is bound to instead. Fixes: 632b2d1deeed ("eal: provide functions

[dpdk-dev] [PATCH v2] bus/pci: use device driver name instead of handler type

2018-10-25 Thread Alejandro Lucero
Invoking the right pci read/write functions is based on interrupt handler type. However, this is not configured for secondary processes precluding to use those functions. This patch fixes the issue using the driver name the device is bound to instead. Fixes: 632b2d1deeed ("eal: provide functions