From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"Ji, Kai" <kai.ji@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH 1/3] crypto/qat: make immutable parameters constant
Date: Mon, 17 Oct 2022 14:58:58 +0000 [thread overview]
Message-ID: <MN2PR11MB3821A47693A5DB2580AF36C1E6299@MN2PR11MB3821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220817065536.79716-2-arkadiuszx.kusztal@intel.com>
Hi Arek,
> -----Original Message-----
> From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> Sent: Wednesday 17 August 2022 07:56
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH 1/3] crypto/qat: make immutable parameters constant
>
> All pointers passed to functions that are not supposed to have its data
> changed should be marked as constant.
> Additionally session field should be checked only in with session case.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/common/qat/qat_adf/qat_pke.h | 16 ++---
> drivers/crypto/qat/qat_asym.c | 133 ++++++++++++++++++---------------
> --
> drivers/crypto/qat/qat_ec.h | 2 +-
> 3 files changed, 76 insertions(+), 75 deletions(-)
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2022-10-17 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 6:55 [PATCH 0/3] crypto/qat: extend asymmetric crypto pmd Arek Kusztal
2022-08-17 6:55 ` [PATCH 1/3] crypto/qat: make immutable parameters constant Arek Kusztal
2022-10-17 14:58 ` Power, Ciara [this message]
2022-08-17 6:55 ` [PATCH 2/3] crypto/qat: add ecdh key exchange algorithm Arek Kusztal
2022-08-17 6:55 ` [PATCH 3/3] crypto/qat: add ecdh public key verification Arek Kusztal
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=MN2PR11MB3821A47693A5DB2580AF36C1E6299@MN2PR11MB3821.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).