From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] fips_validation: fix gcm test
Date: Thu, 14 Jan 2021 15:12:38 +0000 [thread overview]
Message-ID: <VI1PR04MB3168EB58EA291745DD938AA8E6A80@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201022095758.587755-3-roy.fan.zhang@intel.com>
Hi Fan,
> This patch fixes FIPS GCM test of the redundant plaintext string
> write and insufficient test case support check for some corner
> cases.
>
> Fixes: d09abf2d1007 ("examples/fips_validation: update GCM test")
> Cc: roy.fan.zhang@intel.com
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
I believe part of this series is already applied. Please rebase this patchset.
Regards,
Akhil
next prev parent reply other threads:[~2021-01-14 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 9:57 [dpdk-dev] [PATCH 0/2] fips_validation: fix issues Fan Zhang
2020-10-22 9:57 ` [dpdk-dev] [PATCH 1/2] fips_validation: fix missed version line Fan Zhang
2020-10-22 9:57 ` [dpdk-dev] [PATCH 2/2] fips_validation: fix gcm test Fan Zhang
2021-01-14 15:12 ` Akhil Goyal [this message]
2020-10-28 11:44 ` [dpdk-dev] [PATCH 0/2] fips_validation: fix issues 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=VI1PR04MB3168EB58EA291745DD938AA8E6A80@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--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).