From: Harry van Haaren <harry.van.haaren@intel.com>
To: dev@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>, skhare@vmware.com
Subject: [PATCH 18/18] net/vmxnet3: align dynamic log names with standard
Date: Thu, 25 Jan 2018 09:01:10 +0000 [thread overview]
Message-ID: <1516870870-168223-19-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>
---
Maintainer:
Cc: skhare@vmware.com
---
drivers/net/vmxnet3/vmxnet3_ethdev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
index a2fb93c..4e68aae 100644
--- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
+++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
@@ -1352,10 +1352,10 @@ RTE_INIT(vmxnet3_init_log);
static void
vmxnet3_init_log(void)
{
- vmxnet3_logtype_init = rte_log_register("pmd.vmxnet3.init");
+ vmxnet3_logtype_init = rte_log_register("pmd.net.vmxnet3.init");
if (vmxnet3_logtype_init >= 0)
rte_log_set_level(vmxnet3_logtype_init, RTE_LOG_NOTICE);
- vmxnet3_logtype_driver = rte_log_register("pmd.vmxnet3.driver");
+ vmxnet3_logtype_driver = rte_log_register("pmd.net.vmxnet3.driver");
if (vmxnet3_logtype_driver >= 0)
rte_log_set_level(vmxnet3_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 [PATCH 00/18] dynamic logging naming scheme Harry van Haaren
2018-01-25 9:00 ` [PATCH 01/18] doc/contrib: document dynamic logging format Harry van Haaren
2018-01-25 9:23 ` Kovacevic, Marko
2018-01-25 9:00 ` [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 ` [PATCH 03/18] octeontx: align dynamic log names " Harry van Haaren
2018-01-25 11:29 ` Jerin Jacob
2018-01-25 14:19 ` santosh
2018-01-25 9:00 ` [PATCH 04/18] bbdev: " Harry van Haaren
2018-01-25 9:00 ` [PATCH 05/18] net/avf: " Harry van Haaren
2018-01-25 9:00 ` [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 ` [PATCH 07/18] net/e1000: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 08/18] net/ena: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 09/18] net/enic: " Harry van Haaren
2018-01-25 16:30 ` Hyong Youb Kim
2018-01-25 9:01 ` [PATCH 10/18] net/fm10k: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 11/18] net/i40e: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 12/18] net/ixgbe: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 13/18] net/liquidio: " Harry van Haaren
2018-01-27 5:21 ` Shijith Thotton
2018-01-25 9:01 ` [PATCH 14/18] net/nfp: " Harry van Haaren
2018-01-26 11:00 ` Alejandro Lucero
2018-01-25 9:01 ` [PATCH 15/18] net/qede: " Harry van Haaren
2018-01-25 9:01 ` [PATCH 16/18] net/thunderx: " Harry van Haaren
2018-01-25 11:27 ` Jerin Jacob
2018-01-25 9:01 ` [PATCH 17/18] net/virtio: " Harry van Haaren
2018-01-25 11:25 ` Maxime Coquelin
2018-01-25 9:01 ` Harry van Haaren [this message]
2018-01-26 10:14 ` [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-19-git-send-email-harry.van.haaren@intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=skhare@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.