common/octeontx2: remove escape sequences in log
authorStephen Hemminger <stephen@networkplumber.org>
Thu, 11 Jul 2019 03:11:54 +0000 (20:11 -0700)
committerThomas Monjalon <thomas@monjalon.net>
Mon, 15 Jul 2019 22:12:04 +0000 (00:12 +0200)
Putting color escape sequences in the log look pretty for the
developer but fails in real world DPDK usage. A real application
will put DPDK log to syslog, and syslog does not handle escape
sequences.

Fixes: dd543124cd93 ("common/octeontx2: add runtime log infra")

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Jerin Jacob <jerinj@marvell.com>
drivers/common/octeontx2/otx2_common.h

index faf206b..a155462 100644 (file)
@@ -69,12 +69,9 @@ extern int otx2_logtype_tm;
 extern int otx2_logtype_tim;
 extern int otx2_logtype_dpi;
 
-#define OTX2_CLNRM  "\x1b[0m"
-#define OTX2_CLRED  "\x1b[31m"
-
-#define otx2_err(fmt, args...)                                         \
-       RTE_LOG(ERR, PMD, ""OTX2_CLRED"%s():%u " fmt OTX2_CLNRM"\n",    \
-                               __func__, __LINE__, ## args)
+#define otx2_err(fmt, args...)                 \
+       RTE_LOG(ERR, PMD, "%s():%u " fmt "\n",  \
+               __func__, __LINE__, ## args)
 
 #define otx2_info(fmt, args...)                                                \
        RTE_LOG(INFO, PMD, fmt"\n", ## args)