From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>,
Hyong Youb Kim <hyonkim@cisco.com>
Subject: [dpdk-dev] [PATCH 1/3] net/enic: fix whitespaces in log macros
Date: Wed, 30 Oct 2019 22:36:21 -0700 [thread overview]
Message-ID: <20191031053623.16185-2-hyonkim@cisco.com> (raw)
In-Reply-To: <20191031053623.16185-1-hyonkim@cisco.com>
Add a space between the function name and message.
Fixes: bbd8ecc05434 ("net/enic: remove PMD log type references")
Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
Reviewed-by: John Daley <johndale@cisco.com>
---
drivers/net/enic/enic_compat.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/enic/enic_compat.h b/drivers/net/enic/enic_compat.h
index bf9e998a6..bdf4edcab 100644
--- a/drivers/net/enic/enic_compat.h
+++ b/drivers/net/enic/enic_compat.h
@@ -60,8 +60,8 @@ extern int enic_pmd_logtype;
#define ENICPMD_LOG(level, fmt, args...) \
rte_log(RTE_LOG_ ## level, enic_pmd_logtype, \
- "%s" fmt "\n", __func__, ##args)
-#define ENICPMD_FUNC_TRACE() ENICPMD_LOG(DEBUG, " >>")
+ "%s " fmt "\n", __func__, ##args)
+#define ENICPMD_FUNC_TRACE() ENICPMD_LOG(DEBUG, ">>")
#define __le16 u16
#define __le32 u32
--
2.22.0
next prev parent reply other threads:[~2019-10-31 5:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 5:36 [dpdk-dev] [PATCH 0/3] net/enic: fixes for cosmetic issues Hyong Youb Kim
2019-10-31 5:36 ` Hyong Youb Kim [this message]
2019-10-31 5:36 ` [dpdk-dev] [PATCH 2/3] net/enic: fix speed capabilities for the new VF Hyong Youb Kim
2019-10-31 5:36 ` [dpdk-dev] [PATCH 3/3] net/enic: suppress unwanted error messages Hyong Youb Kim
2019-11-06 17:29 ` [dpdk-dev] [PATCH 0/3] net/enic: fixes for cosmetic issues Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191031053623.16185-2-hyonkim@cisco.com \
--to=hyonkim@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).