The rte_errno may be an RTE-specific error code,
use rte_strerror() instead of strerror().

Signed-off-by: Dengdui Huang <huangdeng...@huawei.com>
Acked-by: Chengwen Feng <fengcheng...@huawei.com>
Acked-by: Morten Brørup <m...@smartsharesystems.com>
Acked-by: Huisong Li <lihuis...@huawei.com>
---
 drivers/net/bonding/rte_eth_bond_flow.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/bonding/rte_eth_bond_flow.c 
b/drivers/net/bonding/rte_eth_bond_flow.c
index 5d0be5caf5..a38cc84f56 100644
--- a/drivers/net/bonding/rte_eth_bond_flow.c
+++ b/drivers/net/bonding/rte_eth_bond_flow.c
@@ -31,7 +31,7 @@ bond_flow_alloc(int numa_node, const struct rte_flow_attr 
*attr,
        if (ret < 0) {
                RTE_BOND_LOG(ERR, "Unable to process flow rule (%s): %s",
                             error.message ? error.message : "unspecified",
-                            strerror(rte_errno));
+                            rte_strerror(rte_errno));
                return NULL;
        }
        flow = rte_zmalloc_socket(NULL, offsetof(struct rte_flow, rule) + ret,
@@ -45,7 +45,7 @@ bond_flow_alloc(int numa_node, const struct rte_flow_attr 
*attr,
        if (ret < 0) {
                RTE_BOND_LOG(ERR, "Failed to copy flow rule (%s): %s",
                             error.message ? error.message : "unspecified",
-                            strerror(rte_errno));
+                            rte_strerror(rte_errno));
                rte_free(flow);
                return NULL;
        }
-- 
2.33.0

Reply via email to