The returned error code was wrongly handled causing the PMD to refuse to
start.

Fixes: 91572d2a0b1a ("net/mlx5: fix startup when flow cannot be applied")

CC: sta...@dpdk.org
Signed-off-by: Nelio Laranjeiro <nelio.laranje...@6wind.com>
---
 drivers/net/mlx5/mlx5_trigger.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/mlx5/mlx5_trigger.c b/drivers/net/mlx5/mlx5_trigger.c
index 683b57c..0acbf28 100644
--- a/drivers/net/mlx5/mlx5_trigger.c
+++ b/drivers/net/mlx5/mlx5_trigger.c
@@ -87,7 +87,7 @@ mlx5_dev_start(struct rte_eth_dev *dev)
        if (dev->data->dev_conf.fdir_conf.mode != RTE_FDIR_MODE_NONE)
                priv_fdir_enable(priv);
        err = priv_flow_start(priv);
-       if (!err) {
+       if (err) {
                priv->started = 0;
                ERROR("%p: an error occurred while configuring flows:"
                      " %s",
-- 
2.1.4

Reply via email to