From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, santosh.shukla@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH 03/18] octeontx: align dynamic log names with standard
Date: Thu, 25 Jan 2018 16:59:59 +0530 [thread overview]
Message-ID: <20180125112958.GC7771@jerin> (raw)
In-Reply-To: <1516870870-168223-4-git-send-email-harry.van.haaren@intel.com>
-----Original Message-----
> Date: Thu, 25 Jan 2018 09:00:55 +0000
> 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: [PATCH 03/18] octeontx: align dynamic log names with standard
> X-Mailer: git-send-email 2.7.4
>
> 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>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2018-01-25 11:30 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 ` [dpdk-dev] [PATCH 03/18] octeontx: align dynamic log names " Harry van Haaren
2018-01-25 11:29 ` Jerin Jacob [this message]
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=20180125112958.GC7771@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).