From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] crypto: add user defined name initializing parameter
Date: Mon, 16 Jan 2017 20:00:12 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476C5D35@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1484576095-233208-1-git-send-email-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Monday, January 16, 2017 2:15 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo
> Subject: [PATCH v3 0/2] crypto: add user defined name initializing
> parameter
>
> This patchset adds a user defined name initializing parameter to all
> software cryptodevs.
>
> v3:
> Added name parameter length check
>
> v2:
> Fixed a line adds whitespace error
> Updated rte_cryptodev_version.map
>
> Fan Zhang (2):
> cryptodev: add user defined name initializing parameter to software
> PMD
> crypto: add user defined name initializing parameter parsing to
> software PMDs
>
> drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 58 +++++++++-------------
> --
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 61 +++++++++-----------
> ------
> drivers/crypto/kasumi/rte_kasumi_pmd.c | 58 ++++++++++--------------
> drivers/crypto/null/null_crypto_pmd.c | 55 +++++++++--------------
> drivers/crypto/openssl/rte_openssl_pmd.c | 55 +++++++++--------------
> drivers/crypto/snow3g/rte_snow3g_pmd.c | 59 ++++++++++------------
> ---
> drivers/crypto/zuc/rte_zuc_pmd.c | 59 ++++++++++---------------
> lib/librte_cryptodev/rte_cryptodev.c | 51 +++++++++++++++++++++
> lib/librte_cryptodev/rte_cryptodev.h | 7 ++-
> lib/librte_cryptodev/rte_cryptodev_pmd.h | 7 +++
> lib/librte_cryptodev/rte_cryptodev_version.map | 7 +++
> 11 files changed, 216 insertions(+), 261 deletions(-)
>
> --
> 2.7.4
Combined both patches to avoid compilation breakage.
Applied to dpdk-next-crypto.
Thanks,
Pablo
next prev parent reply other threads:[~2017-01-16 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:13 [dpdk-dev] [PATCH " Fan Zhang
2017-01-11 17:13 ` [dpdk-dev] [PATCH 1/2] cryptodev: add user defined name initializing parameter to software PMD Fan Zhang
2017-01-11 17:13 ` [dpdk-dev] [PATCH 2/2] crypto: add user defined name initializing parameter parsing to software PMDs Fan Zhang
2017-01-12 14:28 ` [dpdk-dev] [PATCH v2 0/2] crypto: add user defined name initializing parameter Fan Zhang
2017-01-12 14:28 ` [dpdk-dev] [PATCH v2 1/2] cryptodev: add user defined name initializing parameter to software PMD Fan Zhang
2017-01-16 14:14 ` [dpdk-dev] [PATCH v3 0/2] crypto: add user defined name initializing parameter Fan Zhang
2017-01-16 14:14 ` [dpdk-dev] [PATCH v3 1/2] cryptodev: add user defined name initializing parameter to software PMD Fan Zhang
2017-01-16 16:01 ` Declan Doherty
2017-01-16 14:14 ` [dpdk-dev] [PATCH v3 2/2] crypto: add user defined name initializing parameter parsing to software PMDs Fan Zhang
2017-01-16 16:01 ` Declan Doherty
2017-01-16 20:00 ` De Lara Guarch, Pablo [this message]
2017-01-12 14:28 ` [dpdk-dev] [PATCH v2 " Fan Zhang
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=E115CCD9D858EF4F90C690B0DCB4D897476C5D35@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--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).