From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH] crypto/libcrypto: fix init function names
Date: Tue, 11 Oct 2016 02:15:05 +0100 [thread overview]
Message-ID: <1476148505-114947-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
All init/uninit function names in the virtual devices have been renamed,
so they finish with probe or remove, so to keep consistency,
same thing should be done in this PMD.
Fixes: d61f70b4c918 ("crypto/libcrypto: add driver for OpenSSL library")
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
drivers/crypto/libcrypto/rte_libcrypto_pmd.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/crypto/libcrypto/rte_libcrypto_pmd.c b/drivers/crypto/libcrypto/rte_libcrypto_pmd.c
index 535fb57..b2c571d 100644
--- a/drivers/crypto/libcrypto/rte_libcrypto_pmd.c
+++ b/drivers/crypto/libcrypto/rte_libcrypto_pmd.c
@@ -42,7 +42,7 @@
#include "rte_libcrypto_pmd_private.h"
-static int cryptodev_libcrypto_uninit(const char *name);
+static int cryptodev_libcrypto_remove(const char *name);
/*----------------------------------------------------------------------------*/
@@ -1008,13 +1008,13 @@ cryptodev_libcrypto_create(const char *name,
init_error:
LIBCRYPTO_LOG_ERR("driver %s: cryptodev_libcrypto_create failed", name);
- cryptodev_libcrypto_uninit(crypto_dev_name);
+ cryptodev_libcrypto_remove(crypto_dev_name);
return -EFAULT;
}
/** Initialise LIBCRYPTO crypto device */
static int
-cryptodev_libcrypto_init(const char *name,
+cryptodev_libcrypto_probe(const char *name,
const char *input_args)
{
struct rte_crypto_vdev_init_params init_params = {
@@ -1037,7 +1037,7 @@ cryptodev_libcrypto_init(const char *name,
/** Uninitialise LIBCRYPTO crypto device */
static int
-cryptodev_libcrypto_uninit(const char *name)
+cryptodev_libcrypto_remove(const char *name)
{
if (name == NULL)
return -EINVAL;
@@ -1050,8 +1050,8 @@ cryptodev_libcrypto_uninit(const char *name)
}
static struct rte_vdev_driver cryptodev_libcrypto_pmd_drv = {
- .probe = cryptodev_libcrypto_init,
- .remove = cryptodev_libcrypto_uninit
+ .probe = cryptodev_libcrypto_probe,
+ .remove = cryptodev_libcrypto_remove
};
DRIVER_REGISTER_VDEV(CRYPTODEV_NAME_LIBCRYPTO_PMD, cryptodev_libcrypto_pmd_drv);
--
2.7.4
next reply other threads:[~2016-10-11 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 1:15 Pablo de Lara [this message]
2016-10-13 17:55 ` Trahe, Fiona
2016-10-13 19:35 ` De Lara Guarch, Pablo
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=1476148505-114947-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
/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).