From: Akhil Goyal <gakhil@marvell.com>
To: Brian Dooley <brian.dooley@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH v1] examples/fips_validation: fix IV generation for gmac
Date: Thu, 3 Nov 2022 11:22:24 +0000 [thread overview]
Message-ID: <CO6PR18MB448463BEECD4C135F8210DC3D8389@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221102120117.381696-1-brian.dooley@intel.com>
> Replace rand() call in fips validation example with rte_rand().
>
> Coverity issue: 381668
> Fixes: e27268bd2103 ("examples/fips_validation: add parsing for AES-GMAC")
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-11-03 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 12:01 Brian Dooley
2022-11-03 11:22 ` 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=CO6PR18MB448463BEECD4C135F8210DC3D8389@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).