From: Akhil Goyal <gakhil@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH v2 0/2] cryptodev: add SM3 and SM4 algorithms
Date: Thu, 29 Sep 2022 19:24:30 +0000 [thread overview]
Message-ID: <CO6PR18MB448429A71C3DA95DCBAF7754D8579@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220928131801.64467-1-arkadiuszx.kusztal@intel.com>
> ShangMi 4 (SM4) is a block cipher used in the Chinese National Standard for
> Wireless LAN WAPI and also used with Transport Layer Security.
> ShangMi 3 (SM3) is a cryptographic hash function used in the
> Chinese National Standard.
>
> This patcheset adds both to the Cryptodev.
>
> v2:
> - Fixed incorrect sm3 string
> - Added full name of the algorithm
>
> Arek Kusztal (2):
> cryptodev: add sm4 encryption algorithm
> cryptodev: add sm3 hash algorithm
>
> doc/guides/cryptodevs/features/default.ini | 4 ++++
> doc/guides/rel_notes/release_22_11.rst | 9 +++++++++
> lib/cryptodev/rte_crypto_sym.h | 13 +++++++++++--
> lib/cryptodev/rte_cryptodev.c | 8 ++++++--
> 4 files changed, 30 insertions(+), 4 deletions(-)
>
Hi Arek,
Why are the QAT implementation patches removed from this series?
We cannot simply add enums which are not being used anywhere.
Regards,
Akhil
next prev parent reply other threads:[~2022-09-29 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 13:17 Arek Kusztal
2022-09-28 13:18 ` [PATCH v2 1/2] cryptodev: add sm4 encryption algorithm Arek Kusztal
2022-09-28 15:26 ` Ji, Kai
2022-09-28 13:18 ` [PATCH v2 2/2] cryptodev: add sm3 hash algorithm Arek Kusztal
2022-09-28 15:27 ` Ji, Kai
2022-09-28 15:29 ` [EXT] [PATCH v2 0/2] cryptodev: add SM3 and SM4 algorithms Anoob Joseph
2022-09-29 19:24 ` Akhil Goyal [this message]
2022-09-30 8:35 ` Kusztal, ArkadiuszX
2022-09-30 8:39 ` Akhil Goyal
2022-09-30 17:43 ` 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=CO6PR18MB448429A71C3DA95DCBAF7754D8579@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@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).