From: Harry van Haaren <harry.van.haaren@intel.com>
To: dev@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>,
santosh.shukla@caviumnetworks.com,
jerin.jacob@caviumnetworks.com
Subject: [dpdk-dev] [PATCH 03/18] octeontx: align dynamic log names with standard
Date: Thu, 25 Jan 2018 09:00:55 +0000 [thread overview]
Message-ID: <1516870870-168223-4-git-send-email-harry.van.haaren@intel.com> (raw)
In-Reply-To: <1516870870-168223-1-git-send-email-harry.van.haaren@intel.com>
This commit aligns the names for dynamic logging with
the newly defined logging format.
Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
---
Maintainers:
Cc: santosh.shukla@caviumnetworks.com
Cc: jerin.jacob@caviumnetworks.com
---
drivers/event/octeontx/ssovf_evdev.c | 2 +-
drivers/mempool/octeontx/octeontx_fpavf.c | 4 ++--
drivers/net/octeontx/octeontx_ethdev.c | 6 +++---
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/event/octeontx/ssovf_evdev.c b/drivers/event/octeontx/ssovf_evdev.c
index edac6d4..a108607 100644
--- a/drivers/event/octeontx/ssovf_evdev.c
+++ b/drivers/event/octeontx/ssovf_evdev.c
@@ -25,7 +25,7 @@ RTE_INIT(otx_ssovf_init_log);
static void
otx_ssovf_init_log(void)
{
- otx_logtype_ssovf = rte_log_register("pmd.otx.eventdev");
+ otx_logtype_ssovf = rte_log_register("pmd.event.octeontx");
if (otx_logtype_ssovf >= 0)
rte_log_set_level(otx_logtype_ssovf, RTE_LOG_NOTICE);
}
diff --git a/drivers/mempool/octeontx/octeontx_fpavf.c b/drivers/mempool/octeontx/octeontx_fpavf.c
index 23e2b9d..61c72c7 100644
--- a/drivers/mempool/octeontx/octeontx_fpavf.c
+++ b/drivers/mempool/octeontx/octeontx_fpavf.c
@@ -112,11 +112,11 @@ RTE_INIT(otx_pool_init_log);
static void
otx_pool_init_log(void)
{
- octeontx_logtype_fpavf = rte_log_register("pmd.otx.mempool");
+ octeontx_logtype_fpavf = rte_log_register("pmd.mempool.octeontx");
if (octeontx_logtype_fpavf >= 0)
rte_log_set_level(octeontx_logtype_fpavf, RTE_LOG_NOTICE);
- octeontx_logtype_fpavf_mbox = rte_log_register("pmd.otx.mempool.mbox");
+ octeontx_logtype_fpavf_mbox = rte_log_register("pmd.mempool.octeontx.mbox");
if (octeontx_logtype_fpavf_mbox >= 0)
rte_log_set_level(octeontx_logtype_fpavf_mbox, RTE_LOG_NOTICE);
}
diff --git a/drivers/net/octeontx/octeontx_ethdev.c b/drivers/net/octeontx/octeontx_ethdev.c
index adca343..06aa0a2 100644
--- a/drivers/net/octeontx/octeontx_ethdev.c
+++ b/drivers/net/octeontx/octeontx_ethdev.c
@@ -49,15 +49,15 @@ RTE_INIT(otx_net_init_log);
static void
otx_net_init_log(void)
{
- otx_net_logtype_mbox = rte_log_register("pmd.otx.ethdev.mbox");
+ otx_net_logtype_mbox = rte_log_register("pmd.net.octeontx.mbox");
if (otx_net_logtype_mbox >= 0)
rte_log_set_level(otx_net_logtype_mbox, RTE_LOG_NOTICE);
- otx_net_logtype_init = rte_log_register("pmd.otx.ethdev.init");
+ otx_net_logtype_init = rte_log_register("pmd.net.octeontx.init");
if (otx_net_logtype_init >= 0)
rte_log_set_level(otx_net_logtype_init, RTE_LOG_NOTICE);
- otx_net_logtype_driver = rte_log_register("pmd.otx.ethdev.driver");
+ otx_net_logtype_driver = rte_log_register("pmd.net.octeontx.driver");
if (otx_net_logtype_driver >= 0)
rte_log_set_level(otx_net_logtype_driver, RTE_LOG_NOTICE);
}
--
2.7.4
next prev parent reply other threads:[~2018-01-25 9:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 9:00 [dpdk-dev] [PATCH 00/18] dynamic logging naming scheme Harry van Haaren
2018-01-25 9:00 ` [dpdk-dev] [PATCH 01/18] doc/contrib: document dynamic logging format Harry van Haaren
2018-01-25 9:23 ` Kovacevic, Marko
2018-01-25 9:00 ` [dpdk-dev] [PATCH 02/18] event/opdl: align dynamic log name with standard Harry van Haaren
2018-01-25 11:15 ` Liang, Ma
2018-01-25 9:00 ` Harry van Haaren [this message]
2018-01-25 11:29 ` [dpdk-dev] [PATCH 03/18] octeontx: align dynamic log names " Jerin Jacob
2018-01-25 14:19 ` santosh
2018-01-25 9:00 ` [dpdk-dev] [PATCH 04/18] bbdev: " Harry van Haaren
2018-01-25 9:00 ` [dpdk-dev] [PATCH 05/18] net/avf: " Harry van Haaren
2018-01-25 9:00 ` [dpdk-dev] [PATCH 06/18] net/avp: " Harry van Haaren
2018-01-25 12:05 ` Legacy, Allain
2018-01-25 17:05 ` Van Haaren, Harry
2018-01-25 17:46 ` Legacy, Allain
2018-01-25 9:00 ` [dpdk-dev] [PATCH 07/18] net/e1000: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 08/18] net/ena: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 09/18] net/enic: " Harry van Haaren
2018-01-25 16:30 ` Hyong Youb Kim
2018-01-25 9:01 ` [dpdk-dev] [PATCH 10/18] net/fm10k: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 11/18] net/i40e: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 12/18] net/ixgbe: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 13/18] net/liquidio: " Harry van Haaren
2018-01-27 5:21 ` Shijith Thotton
2018-01-25 9:01 ` [dpdk-dev] [PATCH 14/18] net/nfp: " Harry van Haaren
2018-01-26 11:00 ` Alejandro Lucero
2018-01-25 9:01 ` [dpdk-dev] [PATCH 15/18] net/qede: " Harry van Haaren
2018-01-25 9:01 ` [dpdk-dev] [PATCH 16/18] net/thunderx: " Harry van Haaren
2018-01-25 11:27 ` Jerin Jacob
2018-01-25 9:01 ` [dpdk-dev] [PATCH 17/18] net/virtio: " Harry van Haaren
2018-01-25 11:25 ` Maxime Coquelin
2018-01-25 9:01 ` [dpdk-dev] [PATCH 18/18] net/vmxnet3: " Harry van Haaren
2018-01-26 10:14 ` [dpdk-dev] [PATCH 00/18] dynamic logging naming scheme Bruce Richardson
2018-01-31 8:28 ` Thomas Monjalon
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=1516870870-168223-4-git-send-email-harry.van.haaren@intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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).