From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH v3] doc: add suggested new feature order to release notes
Date: Mon, 11 Jun 2018 13:11:02 +0100 [thread overview]
Message-ID: <20180611121102.44804-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20180605134424.35529-1-ferruh.yigit@intel.com>
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
---
Cc: Shreyansh Jain <shreyansh.jain@nxp.com>
v2:
* Wording fixed
v3:
* Used suggested multi line format
* added abstraction layer and PMDs order
---
doc/guides/rel_notes/release_18_08.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_08.rst b/doc/guides/rel_notes/release_18_08.rst
index 5bc23c537..b6f0c030e 100644
--- a/doc/guides/rel_notes/release_18_08.rst
+++ b/doc/guides/rel_notes/release_18_08.rst
@@ -37,6 +37,15 @@ New Features
Refer to the previous release notes for examples.
+ Suggested order in release notes items:
+ * Core libs
+ * Device abstraction libs and PMDs
+ + ethdev - ethdev PMDs, cryptodev - cryptodev PMDs, etc..
+ * Other libs
+ * Apps
+ * Examples
+ * Unit tests
+
This section is a comment. Do not overwrite or remove it.
Also, make sure to start the actual text at the margin.
=========================================================
--
2.14.4
prev parent reply other threads:[~2018-06-11 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 9:21 [dpdk-dev] [PATCH] " Ferruh Yigit
2018-06-05 12:36 ` Shreyansh Jain
2018-06-05 13:37 ` Ferruh Yigit
2018-06-05 13:44 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-06-06 9:46 ` Mcnamara, John
2018-06-11 12:11 ` Ferruh Yigit [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=20180611121102.44804-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=shreyansh.jain@nxp.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).