From: Jakub Poczatek <jakub.poczatek@intel.com>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Jakub Poczatek <jakub.poczatek@intel.com>,
stable@dpdk.org, Fan Zhang <roy.fan.zhang@intel.com>
Subject: [PATCH v2] doc: update FIPS docs
Date: Wed, 9 Feb 2022 11:36:23 +0000 [thread overview]
Message-ID: <20220209113623.153785-1-jakub.poczatek@intel.com> (raw)
In-Reply-To: <20220128110801.2573397-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>
---
doc/guides/sample_app_ug/fips_validation.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/guides/sample_app_ug/fips_validation.rst b/doc/guides/sample_app_ug/fips_validation.rst
index 56df434215..39baea3346 100644
--- a/doc/guides/sample_app_ug/fips_validation.rst
+++ b/doc/guides/sample_app_ug/fips_validation.rst
@@ -77,11 +77,12 @@ Compiling the Application
.. code-block:: console
dos2unix AES/req/*
- dos2unix AES_GCM/req/*
+ dos2unix GCM/req/*
dos2unix CCM/req/*
dos2unix CMAC/req/*
dos2unix HMAC/req/*
dos2unix TDES/req/*
+ dos2unix SHA/req/*
Running the Application
-----------------------
--
2.25.1
next parent reply other threads:[~2022-02-09 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220128110801.2573397-1-jakub.poczatek@intel.com>
2022-02-09 11:36 ` Jakub Poczatek [this message]
2022-02-23 9:28 ` [EXT] " 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=20220209113623.153785-1-jakub.poczatek@intel.com \
--to=jakub.poczatek@intel.com \
--cc=dev@dpdk.org \
--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).