From: Akhil Goyal <gakhil@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
Ramkumar Balu <rbalu@marvell.com>
Subject: RE: [EXT] [PATCH 1/4] crypto: add dsa random number k
Date: Mon, 7 Feb 2022 07:33:37 +0000 [thread overview]
Message-ID: <PH0PR18MB44916623232CEED874B997CDD82C9@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220202065030.23276-2-arkadiuszx.kusztal@intel.com>
Hi Arek,
> This commit adds random number 'k' to dsa
> op param struct.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
Could you please update the description of the patches,
To describe the need of the patch and what has been done in the patch.
Most of the commits in this set does not describe the need of the patch.
next prev parent reply other threads:[~2022-02-07 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 6:50 [PATCH 0/4] Clarify asymmetric random, add 'k', uint 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 ` Akhil Goyal [this message]
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 ` [PATCH 0/4] Clarify asymmetric random, add 'k', uint Zhang, Roy Fan
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=PH0PR18MB44916623232CEED874B997CDD82C9@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=rbalu@marvell.com \
--cc=roy.fan.zhang@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).