DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.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>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: Sucharitha Sarananaga <ssarananaga@marvell.com>,
	Abed Mohammad Kamaluddin <akamaluddin@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Archana Muniganti" <marchana@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] examples/fips_validation: fix parsing of cipher length for AES-GCM
Date: Tue, 7 Jan 2020 07:16:34 +0000	[thread overview]
Message-ID: <MN2PR18MB2877937F49E1740DC122CDDEDF3F0@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1578303191-24846-1-git-send-email-marchana@marvell.com>


> -----Original Message-----
> From: Archana Muniganti <marchana@marvell.com>
> Sent: Monday, January 6, 2020 3:03 PM
> To: marko.kovacevic@intel.com; roy.fan.zhang@intel.com;
> akhil.goyal@nxp.com
> Cc: Sucharitha Sarananaga <ssarananaga@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Abed Mohammad Kamaluddin
> <akamaluddin@marvell.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>;
> dev@dpdk.org; stable@dpdk.org; Archana Muniganti
> <marchana@marvell.com>
> Subject: [PATCH] examples/fips_validation: fix parsing of cipher length for AES-
> GCM
> 
> 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>
 
Acked-by: Anoob Joseph <anoobj@marvell.com>

  parent reply	other threads:[~2020-01-07  7:16 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
2020-01-06 13:44   ` Archana Muniganti
2020-01-07  7:16 ` Anoob Joseph [this message]
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=MN2PR18MB2877937F49E1740DC122CDDEDF3F0@MN2PR18MB2877.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=akamaluddin@marvell.com \
    --cc=akhil.goyal@nxp.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).