From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Brian Dooley <brian.dooley@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
Archana Muniganti <marchana@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [PATCH v1 1/2] examples/fips_validation: skip offsetting source for json vectors
Date: Wed, 13 Jul 2022 12:09:31 +0530 [thread overview]
Message-ID: <1daee962c2e3a70b138ea3dd8095dbbaebb1e176.1657694117.git.gmuthukrishn@marvell.com> (raw)
For JSON based test vectors, it is not required to offset further
on source address where key value is read.
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
---
examples/fips_validation/fips_validation.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/examples/fips_validation/fips_validation.c b/examples/fips_validation/fips_validation.c
index 12b9b03f56..c15f0f0202 100644
--- a/examples/fips_validation/fips_validation.c
+++ b/examples/fips_validation/fips_validation.c
@@ -625,7 +625,11 @@ parse_uint8_hex_str(const char *key, char *src, struct fips_val *val)
{
uint32_t len, j;
+#ifndef USE_JANSSON
src += strlen(key);
+#else
+ RTE_SET_USED(key);
+#endif
len = strlen(src) / 2;
--
2.25.1
next reply other threads:[~2022-07-13 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 6:39 Gowrishankar Muthukrishnan [this message]
2022-07-13 6:39 ` [PATCH v1 2/2] examples/fips_validation: add parsing for tdes Gowrishankar Muthukrishnan
2022-08-12 11:52 ` [PATCH v2 1/2] examples/fips_validation: share test callback with multiple keys Gowrishankar Muthukrishnan
2022-08-12 11:52 ` [PATCH v2 2/2] examples/fips_validation: add parsing for TDES Gowrishankar Muthukrishnan
2022-09-23 16:30 ` Dooley, Brian
2022-10-07 9:55 ` Akhil Goyal
2022-10-06 13:13 ` [PATCH v2 1/2] examples/fips_validation: share test callback with multiple keys Dooley, Brian
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=1daee962c2e3a70b138ea3dd8095dbbaebb1e176.1657694117.git.gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=marchana@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).