patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Archana Muniganti <marchana@marvell.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: Sucharitha Sarananaga <ssarananaga@marvell.com>,
	"anoobj@marvell.com" <anoobj@marvell.com>,
	"akamaluddin@marvell.com" <akamaluddin@marvell.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] examples/fips_validation: fix parsing of cipher length for AES-GCM
Date: Mon, 6 Jan 2020 09:38:38 +0000	[thread overview]
Message-ID: <VE1PR04MB66394A6F5C054E371C15D776E63C0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1578303191-24846-1-git-send-email-marchana@marvell.com>

> From: Sucharitha Sarananaga <ssarananaga@marvell.com>
> 
> Cipher length need to be updated in case of AES-GCM decryption.
> 
> Fixes: 4aaad2995e13 ("examples/fips_validation: support GCM parsing")
> 
> Signed-off-by: Archana Muniganti <marchana@marvell.com>
> Signed-off-by: Sucharitha Sarananaga <ssarananaga@marvell.com>
> ---
>  examples/fips_validation/fips_validation_gcm.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/examples/fips_validation/fips_validation_gcm.c
> b/examples/fips_validation/fips_validation_gcm.c
> index ea48ddf..f295025 100644
> --- a/examples/fips_validation/fips_validation_gcm.c
> +++ b/examples/fips_validation/fips_validation_gcm.c
> @@ -19,6 +19,7 @@
>  #define PTLEN_STR	"PTlen = "
>  #define AADLEN_STR	"AADlen = "
>  #define TAGLEN_STR	"Taglen = "
> +#define CTLEN_STR	"PTlen = "
Typo. Should be CTlen

  reply	other threads:[~2020-01-06  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  9:33 Archana Muniganti
2020-01-06  9:38 ` Akhil Goyal [this message]
2020-01-06 13:44   ` Archana Muniganti
2020-01-07  7:16 ` Anoob Joseph
2020-02-05 12:29   ` 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=VE1PR04MB66394A6F5C054E371C15D776E63C0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=akamaluddin@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=marchana@marvell.com \
    --cc=marko.kovacevic@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ssarananaga@marvell.com \
    --cc=stable@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).