From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/6] doc: add empty PMDs todo list
Date: Mon, 11 Dec 2017 11:52:29 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EE1F8F0@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20171121014241.61050-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, November 21, 2017 1:43 AM
> To: Thomas Monjalon <thomas@monjalon.net>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
> Subject: [PATCH 1/6] doc: add empty PMDs todo list
>
> Some library modifications require extra checks or modifications in PMDs
> but currently we don't have a good way to trace these modifications.
>
> And number of these kind of updates increasing by time.
>
> This is an effort to document and track library updates that requires
> attention in PMDs.
>
> Although this is under documentation main use case is for internal
> development.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>...
>
> +PMDs internal TODO list
> +=======================
> +
> +This is the list for tracking required PMD changes triggered by library
> modifications.
> +
> +.. table:: PMDs internal TODO list
> +
> + +------+------+----------+----------------+------+
> + | TODO | PMDs | Deadline | Related Commit | Note |
> + +======+======+==========+================+======+
> + | | | | | |
> + +------+------+----------+----------------+------+
The table should have a label, and it should be indented to the level of .. table
as shown in the guidelines: http://dpdk.org/doc/guides/contributing/documentation.html#rst-guidelines
Something like this:
.. _table_nic_todo:
.. table:: PMDs internal TODO list
+------+------+----------+----------------+------+
| TODO | PMDs | Deadline | Related Commit | Note |
+======+======+==========+================+======+
| | | | | |
+------+------+----------+----------------+------+
However, it isn't an error so:
Acked-by: John McNamara <john.mcnamara@intel.com>
prev parent reply other threads:[~2017-12-11 11:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 1:42 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
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 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE23EE1F8F0@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).