From: Akhil Goyal <gakhil@marvell.com>
To: Jakub Poczatek <jakub.poczatek@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Fan Zhang <roy.fan.zhang@intel.com>
Subject: RE: [EXT] [PATCH v2] doc: update FIPS docs
Date: Wed, 23 Feb 2022 09:28:42 +0000 [thread overview]
Message-ID: <CO6PR18MB44843AE6824FE57FB1AEB6F9D83C9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220209113623.153785-1-jakub.poczatek@intel.com>
> Added missing step for converting SHA request files to correct
> format. Replaced AES_GCM with GCM to follow the correct
> naming format.
>
> Fixes: 3d0fad56b74 ("examples/fips_validation: add crypto FIPS application")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jakub Poczatek <jakub.poczatek@intel.com>
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2022-02-23 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 11:08 [PATCH v1] " Jakub Poczatek
2022-01-28 11:15 ` Zhang, Roy Fan
2022-02-08 21:41 ` [EXT] " Akhil Goyal
2022-02-09 11:36 ` [PATCH v2] " Jakub Poczatek
2022-02-23 9:28 ` 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=CO6PR18MB44843AE6824FE57FB1AEB6F9D83C9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=jakub.poczatek@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=roy.fan.zhang@intel.com \
--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).