From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: fix lists in release notes
Date: Fri, 13 Jul 2018 15:40:08 +0200 [thread overview]
Message-ID: <20180713134008.6837-1-thomas@monjalon.net> (raw)
Some blank lines and hyphens are missing, so lists were badly
interpreted and rendered.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
Already applied.
---
doc/guides/rel_notes/release_18_08.rst | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/doc/guides/rel_notes/release_18_08.rst b/doc/guides/rel_notes/release_18_08.rst
index 550b11049..1274c9210 100644
--- a/doc/guides/rel_notes/release_18_08.rst
+++ b/doc/guides/rel_notes/release_18_08.rst
@@ -117,6 +117,7 @@ API Changes
* cryptodev: Feature flag ``RTE_CRYPTODEV_FF_MBUF_SCATTER_GATHER`` is
replaced with the following more explicit flags:
+
- ``RTE_CRYPTODEV_FF_IN_PLACE_SGL``
- ``RTE_CRYPTODEV_FF_OOP_SGL_IN_SGL_OUT``
- ``RTE_CRYPTODEV_FF_OOP_SGL_IN_LB_OUT``
@@ -127,13 +128,15 @@ API Changes
Used user_data instead of private_data in following APIs to avoid confusion
with the existing session parameter ``sess_private_data[]`` and related APIs.
- ``rte_cryptodev_sym_session_set_private_data()`` changed to
- ``rte_cryptodev_sym_session_set_user_data()``
- ``rte_cryptodev_sym_session_get_private_data()`` changed to
- ``rte_cryptodev_sym_session_get_user_data()``
+
+ - ``rte_cryptodev_sym_session_set_private_data()`` changed to
+ ``rte_cryptodev_sym_session_set_user_data()``
+ - ``rte_cryptodev_sym_session_get_private_data()`` changed to
+ ``rte_cryptodev_sym_session_get_user_data()``
* compressdev: Feature flag ``RTE_COMP_FF_MBUF_SCATTER_GATHER`` is
replaced with the following more explicit flags:
+
- ``RTE_COMP_FF_OOP_SGL_IN_SGL_OUT``
- ``RTE_COMP_FF_OOP_SGL_IN_LB_OUT``
- ``RTE_COMP_FF_OOP_LB_IN_SGL_OUT``
--
2.17.1
reply other threads:[~2018-07-13 13:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180713134008.6837-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
/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).