Re: [dpdk-dev] [PATCH] ethdev: avoid usage of uninit device info in bad port case

2019-07-23 Thread Thomas Monjalon
23/07/2019 14:16, Andrew Rybchenko: > On 7/23/19 1:40 PM, Ferruh Yigit wrote: > > On 7/23/2019 10:13 AM, Andrew Rybchenko wrote: > >> rte_eth_dev_info_get() returns void and caller does know if the function > >> does its job or not. Changing of the return value to int would be > >> API/ABI breakage

Re: [dpdk-dev] [PATCH] ethdev: avoid usage of uninit device info in bad port case

2019-07-23 Thread Andrew Rybchenko
On 7/23/19 1:40 PM, Ferruh Yigit wrote: On 7/23/2019 10:13 AM, Andrew Rybchenko wrote: rte_eth_dev_info_get() returns void and caller does know if the function does its job or not. Changing of the return value to int would be API/ABI breakage which requires deprecation process and cannot be back

Re: [dpdk-dev] [PATCH] ethdev: avoid usage of uninit device info in bad port case

2019-07-23 Thread Ferruh Yigit
On 7/23/2019 10:13 AM, Andrew Rybchenko wrote: > rte_eth_dev_info_get() returns void and caller does know if the function > does its job or not. Changing of the return value to int would be > API/ABI breakage which requires deprecation process and cannot be > backported to stable branches. For now,

[dpdk-dev] [PATCH] ethdev: avoid usage of uninit device info in bad port case

2019-07-23 Thread Andrew Rybchenko
rte_eth_dev_info_get() returns void and caller does know if the function does its job or not. Changing of the return value to int would be API/ABI breakage which requires deprecation process and cannot be backported to stable branches. For now, make sure that device info is initialized even in the