DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
	Vakul Garg <vakul.garg@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: fix SHA256-HMAC digest	length
Date: Wed, 6 Nov 2019 13:17:49 +0000	[thread overview]
Message-ID: <VE1PR04MB663925F314196AC10CF60692E6790@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191106095322.25881-1-akhil.goyal@nxp.com>


> 
> From: Vakul Garg <vakul.garg@nxp.com>
> 
> As per RFC4868, SHA-256 should use 128 bits of ICV.
> Fixes: b5350285ce6e ("examples/ipsec-secgw: support SHA256 HMAC")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Vakul Garg <vakul.garg@nxp.com>
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
> ---
Applied to dpdk-next-crypto



      reply	other threads:[~2019-11-06 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  9:53 Akhil Goyal
2019-11-06 13:17 ` Akhil Goyal [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=VE1PR04MB663925F314196AC10CF60692E6790@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=stable@dpdk.org \
    --cc=vakul.garg@nxp.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).