From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"Tomasz Duszynski" <tdu@semihalf.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] examples/ipsec-secgw: set ip6_plen to the proper value
Date: Thu, 19 Oct 2017 19:12:31 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC3805F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <c5bbeb45-b4ca-d3ad-4698-c1433804ae2e@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Wednesday, October 18, 2017 5:18 PM
> To: Tomasz Duszynski <tdu@semihalf.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: set ip6_plen to the
> proper value
>
> On 13/10/2017 09:04, Tomasz Duszynski wrote:
> > ipv6 payload length header field should contain only the number of
> > bytes following the ipv6 header and not the entire packet size.
> >
> > Fixes: f159e70b0922 ("examples/ipsec-secgw: support transport mode")
> > Fixes: 906257e965b7 ("examples/ipsec-secgw: support IPv6")
> >
> > Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
> > ---
> > examples/ipsec-secgw/esp.c | 6 ++++--
> > examples/ipsec-secgw/ipip.h | 3 ++-
> > 2 files changed, 6 insertions(+), 3 deletions(-)
>
> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
CC'ing stable ML.
Applied to dpdk-next-crypto.
Thanks,
Pablo
parent reply other threads:[~2017-10-19 19:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c5bbeb45-b4ca-d3ad-4698-c1433804ae2e@intel.com>]
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=E115CCD9D858EF4F90C690B0DCB4D8976CC3805F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=stable@dpdk.org \
--cc=tdu@semihalf.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).