From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, konstantin.ananyev@intel.com, akhil.goyal@nxp.com,
john.mcnamara@intel.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH v3] doc: release note for the IPsec library
Date: Thu, 25 Jul 2019 15:39:25 +0100 [thread overview]
Message-ID: <1564065565-24563-1-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1564059485-12122-1-git-send-email-bernard.iremonger@intel.com>
Update release notes for changes to the IPsec library.
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
changes in v3:
revised content
doc/guides/rel_notes/release_19_08.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/rel_notes/release_19_08.rst b/doc/guides/rel_notes/release_19_08.rst
index c9bd3ce..7737ebe 100644
--- a/doc/guides/rel_notes/release_19_08.rst
+++ b/doc/guides/rel_notes/release_19_08.rst
@@ -224,6 +224,14 @@ New Features
Added multiple cores feature to compression perf tool application.
+* **Updated the IPsec library.**
+
+ Added the following functionality to ``librte_ipsec``.
+
+ * Added support for transport mode with IPv6 extension headers.
+
+ * Added support for packets that consist of multiple segments.
+
Removed Items
-------------
--
2.7.4
next prev parent reply other threads:[~2019-07-25 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:59 [dpdk-dev] [PATCH] " Bernard Iremonger
2019-07-25 12:58 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2019-07-25 14:39 ` Bernard Iremonger [this message]
2019-07-25 14:52 ` [dpdk-dev] [PATCH v3] " Ananyev, Konstantin
2019-07-26 10:27 ` Akhil Goyal
2019-07-26 10:49 ` Iremonger, Bernard
2019-07-26 11:57 ` [dpdk-dev] [PATCH v4] doc: release note for the IPsec library and application Bernard Iremonger
2019-07-26 12:36 ` Akhil Goyal
2019-07-26 13:17 ` Iremonger, Bernard
2019-07-26 13:42 ` [dpdk-dev] [PATCH v5] " Bernard Iremonger
2019-07-26 13:44 ` Akhil Goyal
2019-07-26 13:54 ` Akhil Goyal
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=1564065565-24563-1-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
/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).