From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/6] doc: add dynamic logging to PMD todo list
Date: Fri, 8 Dec 2017 10:42:21 +0530 [thread overview]
Message-ID: <eeafbd4f-2832-0135-0c8d-313de7456738@nxp.com> (raw)
In-Reply-To: <20171121014241.61050-3-ferruh.yigit@intel.com>
On 11/21/2017 7:12 AM, Ferruh Yigit wrote:
> To track modification:
> c1b5fa94a46f ("eal: support dynamic log types")
>
> Proposed deadline for PMDs is v18.08
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> doc/guides/nics/todo.rst | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/doc/guides/nics/todo.rst b/doc/guides/nics/todo.rst
> index b408fc691..973379a3d 100644
> --- a/doc/guides/nics/todo.rst
> +++ b/doc/guides/nics/todo.rst
> @@ -50,3 +50,14 @@ This is the list for tracking required PMD changes triggered by library modifica
> | | | thunderx, vhost, | | | |
> | | | vmxnet3 | | | |
> +-------------------+--------------------------------+----------+----------------+-----------------------------------+
> + | dynamic logging | | af_packet, ark, avp, bnx2x, | v18.08 | c1b5fa94a46f | Switch to dynamic logging |
> + | | | bnxt, bonding, cxgbe, dpaa, | | | functions, remove static debug |
> + | | | dpaa2, e1000, ena, enic, | | | config options. |
> + | | | failsafe, fm10k, ixgbe, | | | |
> + | | | kni, liquidio, mlx4, mlx5, | | | |
> + | | | mrvl, nfp, null, octeontx, | | | |
> + | | | pcap, qede, ring, sfc, | | | |
> + | | | softnic, szedata2, tap, | | | |
> + | | | thunderx, vhost, virtio, | | | |
> + | | | vmxnet3 | | | |
> + +-------------------+--------------------------------+----------+----------------+-----------------------------------+
>
One small correction - dpaa is already supporting dynamic logging.
It is a good idea to have todo item documented.
Series-acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2017-12-08 5:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 1:42 [dpdk-dev] [PATCH 1/6] doc: add empty PMDs " Ferruh Yigit
2017-11-21 1:42 ` [dpdk-dev] [PATCH 2/6] doc: add mbuf reorg to PMD " Ferruh Yigit
2017-12-11 14:00 ` Marko Kovacevic
2017-12-11 14:09 ` Mcnamara, John
2017-12-29 11:58 ` Andrew Rybchenko
2017-12-29 17:07 ` Stephen Hemminger
2018-01-03 14:00 ` Olivier Matz
2017-11-21 1:42 ` [dpdk-dev] [PATCH 3/6] doc: add dynamic logging " Ferruh Yigit
2017-12-08 5:12 ` Hemant Agrawal [this message]
2017-12-11 14:09 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 4/6] doc: add descriptor status API " Ferruh Yigit
2017-12-11 14:11 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 5/6] doc: add offload flag " Ferruh Yigit
2017-11-21 8:32 ` Shahaf Shuler
2017-11-21 18:02 ` Ferruh Yigit
2017-11-22 8:43 ` Shahaf Shuler
2017-11-22 8:54 ` Thomas Monjalon
2017-12-11 14:11 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 6/6] doc: add mbuf VLAN " Ferruh Yigit
2017-11-21 1:53 ` Ferruh Yigit
2017-12-06 9:24 ` Hemant Agrawal
2017-12-11 14:16 ` Mcnamara, John
2017-12-29 11:50 ` Andrew Rybchenko
2017-12-29 17:09 ` Stephen Hemminger
2018-01-03 14:14 ` Olivier Matz
2017-12-11 11:52 ` [dpdk-dev] [PATCH 1/6] doc: add empty PMDs " Mcnamara, John
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=eeafbd4f-2832-0135-0c8d-313de7456738@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--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).