DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 1/6] doc: add empty PMDs todo list
Date: Tue, 21 Nov 2017 01:42:36 +0000	[thread overview]
Message-ID: <20171121014241.61050-1-ferruh.yigit@intel.com> (raw)

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>
---
 MAINTAINERS               |  1 +
 doc/guides/nics/index.rst |  1 +
 doc/guides/nics/todo.rst  | 43 +++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 45 insertions(+)
 create mode 100644 doc/guides/nics/todo.rst

diff --git a/MAINTAINERS b/MAINTAINERS
index f0baeb423..c9eaff774 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -315,6 +315,7 @@ Networking Drivers
 M: Ferruh Yigit <ferruh.yigit@intel.com>
 T: git://dpdk.org/next/dpdk-next-net
 F: doc/guides/nics/features/default.ini
+F: doc/guides/nics/todo.rst
 
 Link bonding
 M: Declan Doherty <declan.doherty@intel.com>
diff --git a/doc/guides/nics/index.rst b/doc/guides/nics/index.rst
index 23babe933..f257fbd87 100644
--- a/doc/guides/nics/index.rst
+++ b/doc/guides/nics/index.rst
@@ -37,6 +37,7 @@ Network Interface Controller Drivers
 
     overview
     features
+    todo
     build_and_test
     ark
     avp
diff --git a/doc/guides/nics/todo.rst b/doc/guides/nics/todo.rst
new file mode 100644
index 000000000..874811ad5
--- /dev/null
+++ b/doc/guides/nics/todo.rst
@@ -0,0 +1,43 @@
+..  BSD LICENSE
+    Copyright(c) 2017 Intel Corporation. All rights reserved.
+    All rights reserved.
+
+    Redistribution and use in source and binary forms, with or without
+    modification, are permitted provided that the following conditions
+    are met:
+
+    * Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+    * Neither the name of Intel Corporation nor the names of its
+    contributors may be used to endorse or promote products derived
+    from this software without specific prior written permission.
+
+    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+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 |
+ +======+======+==========+================+======+
+ |      |      |          |                |      |
+ +------+------+----------+----------------+------+
-- 
2.13.6

             reply	other threads:[~2017-11-21  1:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  1:42 Ferruh Yigit [this message]
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 ` [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=20171121014241.61050-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --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).