From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix list of unsupported features for IPsec lib
Date: Tue, 1 Oct 2019 16:26:54 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260DFF506@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20190927142042.27513-1-konstantin.ananyev@intel.com>
Hi Konstantin,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Konstantin
> Ananyev
> Sent: Friday, September 27, 2019 3:21 PM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: fix list of unsupported features for IPsec lib
>
> List of unsupported features doesn't reflect latest changes.
>
> Fixes: cd5b860c1851 ("ipsec: support header construction")
> Fixes: 2c1887fad075 ("ipsec: fix transport mode for IPv6 with extensions")
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
> doc/guides/prog_guide/ipsec_lib.rst | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/doc/guides/prog_guide/ipsec_lib.rst
> b/doc/guides/prog_guide/ipsec_lib.rst
> index 63b75b652..17d9da28f 100644
> --- a/doc/guides/prog_guide/ipsec_lib.rst
> +++ b/doc/guides/prog_guide/ipsec_lib.rst
> @@ -161,7 +161,4 @@ Limitations
>
> The following features are not properly supported in the current version:
>
> -* ESP transport mode for IPv6 packets with extension headers.
> -* Updates of the fields in inner IP header for tunnel mode
> - (as described in RFC 4301, section 5.1.2).
> * Hard/soft limit for SA lifetime (time interval/byte count).
> --
> 2.17.1
./devtools/check-git-log.sh -1
Is it candidate for Cc: stable@dpdk.org backport?
doc: fix list of unsupported features for IPsec lib
Otherwise
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
next prev parent reply other threads:[~2019-10-01 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 14:20 Konstantin Ananyev
2019-10-01 16:26 ` Iremonger, Bernard [this message]
2019-10-01 17:27 ` Ananyev, Konstantin
2019-10-17 9:57 ` 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=8CEF83825BEC744B83065625E567D7C260DFF506@IRSMSX108.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--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).