DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: RE: [PATCH] examples/fips_validation: fix digest in non JSON SHA MCT
Date: Tue, 28 Mar 2023 06:40:25 +0000	[thread overview]
Message-ID: <CO6PR18MB448401336C07F1E78E144E0AD8889@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB18486BDB8C4A065DA1DF1A5983849@CY4PR11MB1848.namprd11.prod.outlook.com>

> Hi Gowrishankar,
> > Subject: [PATCH] examples/fips_validation: fix digest in non JSON SHA MCT
> >
> > Non JSON SHA MCT tests produce incorrect digest due to a regression while
> > handling MD blocks in common for all kind of SHA, SHA2, SHA3 and SHAKE
> > algorithms. Fixing this along with some cleanup to use only rte_malloc API for
> > storing test vectors as in other tests.
> >
> > Fixes: d8417b5ef4e ("examples/fips_validation: add SHA3 validation")
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Tested-by: Brian Dooley <brian.dooley@intel.com>

Applied to dpdk-next-crypto
Fixes tag changed to 
1ea7940e0f44 ("examples/fips_validation: add SHA3 validation")

Thanks.

      reply	other threads:[~2023-03-28  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  9:02 Gowrishankar Muthukrishnan
2023-03-24 15:01 ` Dooley, Brian
2023-03-28  6:40   ` 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=CO6PR18MB448401336C07F1E78E144E0AD8889@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gmuthukrishn@marvell.com \
    --cc=jerinj@marvell.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).