Re: [dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd on null drv opts

Acked-by: Viacheslav Ovsiienko Thanks > -Original Message- > From: dev On Behalf Of Moti Haimovsky > Sent: Wednesday, June 19, 2019 7:52 > To: Shahaf Shuler > Cc: dev@dpdk.org; sta...@dpdk.org > Subject: [dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd

[dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd on null drv opts

mlx5 implements mlx5_flow_null_drv_ops to be used when a specific flow typei/driver is not available or invalid. This routines return error without modifying the rte_flow_error parameter passed to them which causes testpmd, for example, to crash. This commit addresses the issue by modifying the rte

[dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd on null drv opts

mlx5 implements mlx5_flow_null_drv_ops to be used when a specific flow typei/driver is not available or invalid. This routines return error without modifying the rte_flow_error parameter passed to them which causes testpmd, for example, to crash. This commit addresses the issue by modifying the rte

[dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd on null drv opts

mlx5 implements mlx5_flow_null_drv_ops to be used when a specific flow typei/driver is not available or invalid. This routines return error without modifying the rte_flow_error parameter passed to them which causes testpmd, for example, to crash. This commit addresses the issue by modifying the rte

[dpdk-dev] [PATCH v5 1/2] net/mlx5: fix crashing testpmd on null drv opts

mlx5 implements mlx5_flow_null_drv_ops to be used when a specific flow typei/driver is not available or invalid. This routines return error without modifying the rte_flow_error parameter passed to them which causes testpmd, for example, to crash. This commit addresses the issue by modifying the rte