From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>
Subject: Re: [dpdk-dev] [PATCH] openssl pmd: rename SW crypto device from libcrypto to openssl
Date: Thu, 20 Oct 2016 20:44:44 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973CA15E4C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <A09C9DDE180C7E429EC68E2BFB95C90339479F6D@IRSMSX107.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jain, Deepak K
> Sent: Wednesday, October 19, 2016 1:27 AM
> To: Mrozowicz, SlawomirX; Doherty, Declan
> Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> Subject: Re: [dpdk-dev] [PATCH] openssl pmd: rename SW crypto device from
> libcrypto to openssl
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Slawomir
> > Mrozowicz
> > Sent: Tuesday, October 18, 2016 12:36 PM
> > To: Doherty, Declan <declan.doherty@intel.com>
> > Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> > <slawomirx.mrozowicz@intel.com>
> > Subject: [dpdk-dev] [PATCH] openssl pmd: rename SW crypto device from
> > libcrypto to openssl
> >
> > This patch replaces name "libcrypto" to "openssl" from file directories,
> > symbol prefixes and sub-names connected with old name.
> > Renamed poll mode driver files, test files, and documentations.
> > It is done to better name association with library because
> > the cryptography operations are using Openssl library crypto API.
> >
> > Fixes: d61f70b4c918 ("crypto/libcrypto: add driver for OpenSSL library")
> >
> > Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> > ---
> > MAINTAINERS | 6 +-
> > app/test/test_cryptodev.c | 56 +-
> > app/test/test_cryptodev_aes_test_vectors.h | 62 +-
> > app/test/test_cryptodev_blockcipher.c | 6 +-
> > app/test/test_cryptodev_blockcipher.h | 2 +-
> > app/test/test_cryptodev_des_test_vectors.h | 56 +-
> > app/test/test_cryptodev_hash_test_vectors.h | 48 +-
> > app/test/test_cryptodev_perf.c | 52 +-
> > config/common_base | 4 +-
> > delete mode 100644
> > drivers/crypto/libcrypto/rte_pmd_libcrypto_version.map
> > create mode 100644 drivers/crypto/openssl/Makefile
> > create mode 100644 drivers/crypto/openssl/rte_openssl_pmd.c
> > create mode 100644 drivers/crypto/openssl/rte_openssl_pmd_ops.c
> > create mode 100644 drivers/crypto/openssl/rte_openssl_pmd_private.h
> > create mode 100644
> drivers/crypto/openssl/rte_pmd_openssl_version.map
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 8f5fa82..af47e04 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > --
> > 2.5.0
> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2016-10-20 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 11:36 Slawomir Mrozowicz
2016-10-19 8:27 ` Jain, Deepak K
2016-10-20 20:44 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8973CA15E4C@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).