DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Anoob Joseph <anoobj@marvell.com>
Cc: Marko Kovacevic <marko.kovacevic@intel.com>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	 Narayana Prasad <pathreya@marvell.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,  "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] examples/fips_validation: fix incorrect string for CT length
Date: Thu, 20 Feb 2020 16:48:25 +0100	[thread overview]
Message-ID: <CAJFAV8yROaxoTfKATL5D3y+CNxmC7Bewxow7=9La2t3JVPh_jA@mail.gmail.com> (raw)
In-Reply-To: <VE1PR04MB6639BCF806B4FB4559B5C894E6130@VE1PR04MB6639.eurprd04.prod.outlook.com>

On Thu, Feb 20, 2020 at 11:15 AM Akhil Goyal <akhil.goyal@nxp.com> wrote:
> > The NIST test vectors use the string 'PTlen' to denote text lengths
> > in case of encrypt & decrypt operations. So the same string need to be
> > used while parsing PT and CT.
> >
> > Fixes: 2adb3b4e7e54 ("examples/fips_validation: fix AES-GCM cipher length
> > parsing")
> >
> > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> > ---
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied, thanks.


-- 
David Marchand


      parent reply	other threads:[~2020-02-20 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  9:44 [dpdk-dev] [PATCH] examples/fips_validation: fix incorrect CT length string Anoob Joseph
2020-02-18 10:31 ` [dpdk-dev] [PATCH v2] examples/fips_validation: fix incorrect string for CT length Anoob Joseph
2020-02-19 10:22   ` Anoob Joseph
2020-02-20 10:15   ` Akhil Goyal
2020-02-20 10:19     ` David Marchand
2020-02-20 15:48     ` David Marchand [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='CAJFAV8yROaxoTfKATL5D3y+CNxmC7Bewxow7=9La2t3JVPh_jA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=pathreya@marvell.com \
    --cc=roy.fan.zhang@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).