From: "Dooley, Brian" <brian.dooley@intel.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH v1] examples/fips_validation: fix parsing SHA test type from JSON vector
Date: Fri, 23 Sep 2022 16:25:41 +0000 [thread overview]
Message-ID: <CY4PR11MB1848C319CE38DA47F84634C983519@CY4PR11MB1848.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220812114910.1032234-1-gmuthukrishn@marvell.com>
> -----Original Message-----
> From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Sent: Friday, August 12, 2022 12:49 PM
> To: dev@dpdk.org
> Cc: Anoob Joseph <anoobj@marvell.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; Dooley, Brian <brian.dooley@intel.com>; Akhil
> Goyal <gakhil@marvell.com>; Gowrishankar Muthukrishnan
> <gmuthukrishn@marvell.com>
> Subject: [PATCH v1] examples/fips_validation: fix parsing SHA test type from
> JSON vector
>
> Store SHA test type in its own interim info struct instead of AES.
>
> Fixes: d5c247145c2 ("examples/fips_validation: add parsing for SHA")
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> examples/fips_validation/fips_validation_sha.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/fips_validation/fips_validation_sha.c
> b/examples/fips_validation/fips_validation_sha.c
> index dff552586f..75b073c15d 100644
> --- a/examples/fips_validation/fips_validation_sha.c
> +++ b/examples/fips_validation/fips_validation_sha.c
> @@ -259,7 +259,7 @@ parse_test_sha_json_test_type(void)
>
> for (i = 0; i < RTE_DIM(sha_test_types); i++)
> if (strstr(type_str, sha_test_types[i].desc)) {
> - info.interim_info.aes_data.test_type =
> + info.interim_info.sha_data.test_type =
> sha_test_types[i].type;
> break;
> }
> --
> 2.25.1
LGTM
Tested-by: Brian Dooley <brian.dooley@intel.com>
next prev parent reply other threads:[~2022-09-23 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 11:49 Gowrishankar Muthukrishnan
2022-09-23 16:25 ` Dooley, Brian [this message]
2022-10-07 10:40 ` 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=CY4PR11MB1848C319CE38DA47F84634C983519@CY4PR11MB1848.namprd11.prod.outlook.com \
--to=brian.dooley@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@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).