From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, fiona.trahe@intel.com,
shally.verma@caviumnetworks.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/3] crypotodev: add result field to modular operations
Date: Fri, 8 Feb 2019 12:13:35 +0100 [thread overview]
Message-ID: <20190208111338.4544-1-arkadiuszx.kusztal@intel.com> (raw)
This patchset adds result field to modular exponentiation and modular
inverse operations
This patchset depends on following patches:
[1] - "[v3] cryptodev: rework mod exp and mod inv comments"
(http://patchwork.dpdk.org/patch/50139/)
[2] - "openssl: fix bad reference of modinv"
(http://patchwork.dpdk.org/patch/50131/)
v2:
- fix checkpatch issue
Arek Kusztal (3):
cryptodev: add result field to mod exp and inverse operations
openssl: add result field to mod exp and mod inv operations
test: add result field to mod exp and mod inv
drivers/crypto/openssl/rte_openssl_pmd.c | 4 ++--
lib/librte_cryptodev/rte_crypto_asym.h | 10 ++++++++++
test/test/test_cryptodev_asym.c | 6 ++++++
test/test/test_cryptodev_asym_util.h | 8 ++++----
4 files changed, 22 insertions(+), 6 deletions(-)
--
2.1.0
next reply other threads:[~2019-02-08 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:13 Arek Kusztal [this message]
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 1/3] cryptodev: add result field to mod exp and inverse operations Arek Kusztal
2019-02-12 10:55 ` Shally Verma
2019-02-28 9:59 ` Akhil Goyal
2019-02-28 10:44 ` Kusztal, ArkadiuszX
2019-02-28 10:52 ` Akhil Goyal
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 2/3] openssl: add result field to mod exp and mod inv operations Arek Kusztal
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 3/3] test: add result field to mod exp and mod inv Arek Kusztal
2019-02-12 11:00 ` Shally Verma
2019-02-08 12:31 ` [dpdk-dev] [PATCH v2 0/3] crypotodev: add result field to modular operations Trahe, Fiona
2019-03-19 14:02 ` Akhil Goyal
2019-03-19 14:02 ` 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=20190208111338.4544-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=shally.verma@caviumnetworks.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).