From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH v4 3/3] eal: don't enable static log macro for ethdev
Date: Tue, 19 Jun 2018 02:04:57 +0100 [thread overview]
Message-ID: <20180619010457.61490-3-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20180619010457.61490-1-ferruh.yigit@intel.com>
static logging macro RTE_PMD_DEBUG_TRACE is enabled with a few DEBUG
config options, including RTE_LIBRTE_ETHDEV_DEBUG
RTE_LIBRTE_ETHDEV_DEBUG is still used for data path logging, but all
ethdev logging switched to dynamic logging, so no need to enable static
logging macro for ethdev.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
lib/librte_eal/common/include/rte_dev.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
index 3879ff3ca..ba6e445fc 100644
--- a/lib/librte_eal/common/include/rte_dev.h
+++ b/lib/librte_eal/common/include/rte_dev.h
@@ -69,8 +69,7 @@ rte_pmd_debug_trace(const char *func_name, const char *fmt, ...)
* Enable RTE_PMD_DEBUG_TRACE() when at least one component relying on the
* RTE_*_RET() macros defined below is compiled in debug mode.
*/
-#if defined(RTE_LIBRTE_ETHDEV_DEBUG) || \
- defined(RTE_LIBRTE_CRYPTODEV_DEBUG) || \
+#if defined(RTE_LIBRTE_CRYPTODEV_DEBUG) || \
defined(RTE_LIBRTE_EVENTDEV_DEBUG)
#define RTE_PMD_DEBUG_TRACE(...) \
rte_pmd_debug_trace(__func__, __VA_ARGS__)
--
2.17.1
next prev parent reply other threads:[~2018-06-19 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 17:28 [dpdk-dev] [PATCH 1/2] ethdev: move log macro to header Ferruh Yigit
2018-05-01 17:28 ` [dpdk-dev] [PATCH 2/2] ethdev: convert static logtype usage to dynamic Ferruh Yigit
2018-05-01 18:56 ` [dpdk-dev] [PATCH 1/2] ethdev: move log macro to header Thomas Monjalon
2018-05-02 9:40 ` Ferruh Yigit
2018-05-02 14:45 ` Stephen Hemminger
2018-05-09 14:24 ` [dpdk-dev] [PATCH v2 " Ferruh Yigit
2018-05-09 14:24 ` [dpdk-dev] [PATCH v2 2/2] ethdev: convert static logtype usage to dynamic Ferruh Yigit
2018-05-14 15:56 ` [dpdk-dev] [PATCH v3 1/2] ethdev: move log macro to header Ferruh Yigit
2018-05-14 15:56 ` [dpdk-dev] [PATCH v3 2/2] ethdev: convert static logtype usage to dynamic Ferruh Yigit
2018-06-19 1:04 ` [dpdk-dev] [PATCH v4 1/3] ethdev: move log macro to header Ferruh Yigit
2018-06-19 1:04 ` [dpdk-dev] [PATCH v4 2/3] ethdev: convert static logtype usage to dynamic Ferruh Yigit
2018-06-19 13:11 ` Andrew Rybchenko
2018-06-19 1:04 ` Ferruh Yigit [this message]
2018-06-19 13:02 ` [dpdk-dev] [PATCH v4 1/3] ethdev: move log macro to header Andrew Rybchenko
2018-06-26 11:41 ` Shahaf Shuler
2018-06-26 12:25 ` Thomas Monjalon
2018-06-26 15:52 ` 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=20180619010457.61490-3-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).