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>
Subject: RE: [PATCH v2 1/2] crypto/qat: refactor asym algorithm macros and logs
Date: Tue, 10 May 2022 10:08:28 +0000 [thread overview]
Message-ID: <MW5PR11MB5809280E006F1EF8DCD08D4DB8C99@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220422093355.13631-2-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Friday, April 22, 2022 10:34 AM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v2 1/2] crypto/qat: refactor asym algorithm macros and logs
>
> This commit unifies macros for asymmetric parameters,
> therefore making code easier to maintain.
> It additionally changes some of PMD output logs that
> right now can only be seen in debug mode.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/crypto/qat/qat_asym.c | 230 ++++++++++++++++++-------------------
> -----
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-05-10 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:33 [PATCH v2 0/2] crypto/qat: add secp384r1 curve support Arek Kusztal
2022-04-22 9:33 ` [PATCH v2 1/2] crypto/qat: refactor asym algorithm macros and logs Arek Kusztal
2022-05-10 10:08 ` Zhang, Roy Fan [this message]
2022-04-22 9:33 ` [PATCH v2 2/2] crypto/qat: add secp384r1 curve Arek Kusztal
2022-05-10 10:10 ` Zhang, Roy Fan
2022-05-10 10:10 ` [PATCH v2 0/2] crypto/qat: add secp384r1 curve support Zhang, Roy Fan
2022-05-26 16:53 ` 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=MW5PR11MB5809280E006F1EF8DCD08D4DB8C99@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@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).