From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"rbalu@marvell.com" <rbalu@marvell.com>
Subject: RE: [PATCH 0/4] Clarify asymmetric random, add 'k', uint
Date: Fri, 4 Feb 2022 10:03:26 +0000 [thread overview]
Message-ID: <MW5PR11MB5809ED7EC8147A441D94FA1CB8299@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220202065030.23276-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Wednesday, February 2, 2022 6:50 AM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> rbalu@marvell.com; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH 0/4] Clarify asymmetric random, add 'k', uint
>
> This patchset introduces following changes:
>
> 1) DSA 'k' was added that devices withouth random support can work.
> 2) Clarified usage of random numbers in asym, as per discussion
> from December.
> 3) Added typedef for crypto_uint to remove some repeating
> comments making code more readable. Additionally some rearrangement
> were made to improve readibility.
>
> Arek Kusztal (4):
> crypto: add dsa random number k
> crypto: clarify usage of random numbers in asym
> crypto: use rte macro instead of direct attribute
> crypto: reorganize endianness comments, add crypto uint
>
> lib/cryptodev/rte_crypto_asym.h | 363 ++++++++++++++++-------------------
> -----
> 1 file changed, 141 insertions(+), 222 deletions(-)
>
> --
> 2.13.6
Series-acked-by: Fan Zhang <roy.fan.zhang@intel.com>
prev parent reply other threads:[~2022-02-04 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 6:50 Arek Kusztal
2022-02-02 6:50 ` [PATCH 1/4] crypto: add dsa random number k Arek Kusztal
2022-02-04 10:02 ` Zhang, Roy Fan
2022-02-07 7:33 ` [EXT] " Akhil Goyal
2022-02-02 6:50 ` [PATCH 2/4] crypto: clarify usage of random numbers in asym Arek Kusztal
2022-02-04 10:03 ` Zhang, Roy Fan
2022-02-02 6:50 ` [PATCH 3/4] crypto: use rte macro instead of direct attribute Arek Kusztal
2022-02-04 10:04 ` Zhang, Roy Fan
2022-02-02 6:50 ` [PATCH 4/4] crypto: reorganize endianness comments, add crypto uint Arek Kusztal
2022-02-04 10:04 ` Zhang, Roy Fan
2022-02-04 10:03 ` Zhang, Roy Fan [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=MW5PR11MB5809ED7EC8147A441D94FA1CB8299@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=rbalu@marvell.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).