Re: [dpdk-dev] [PATCH] kni: fix pci_enable_msix_range error handling

2018-02-05 Thread Andy Roulin
Hi Ferruh, You can drop it then. I encountered the same porting bug in another project and came across dpdk's code and patchwork comments which helped me debugging. I just thought I would contribute the fix back. If it's not functional then just drop it :) Andy On Mon, Feb 5, 2018 at 11:05 AM F

Re: [dpdk-dev] [PATCH] kni: fix pci_enable_msix_range error handling

2018-02-05 Thread Ferruh Yigit
On 12/18/2017 6:16 AM, Andy Roulin wrote: > pci_enable_msix_range's return value has a different meaning than what > was previously returned by pci_enable_msix. > > "It returns a negative errno if an error occurs. If it succeeds, it > returns the actual number of interrupts allocated and indicates

[dpdk-dev] [PATCH] kni: fix pci_enable_msix_range error handling

2017-12-17 Thread Andy Roulin
pci_enable_msix_range's return value has a different meaning than what was previously returned by pci_enable_msix. "It returns a negative errno if an error occurs. If it succeeds, it returns the actual number of interrupts allocated and indicates the successful configuration of MSI-X capability st