From: Bruce Richardson <bruce.richardson@intel.com>
To: pablo.de.lara.guarch@intel.com, declan.doherty@intel.com,
jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: rename map file to standard name
Date: Thu, 14 Sep 2017 17:02:13 +0100 [thread overview]
Message-ID: <20170914160214.94767-2-bruce.richardson@intel.com> (raw)
In-Reply-To: <20170914160214.94767-1-bruce.richardson@intel.com>
Naming convention for crypto drivers is "rte_pmd_<name>_version.map"
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
drivers/crypto/aesni_mb/Makefile | 2 +-
.../{rte_pmd_aesni_version.map => rte_pmd_aesni_mb_version.map} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename drivers/crypto/aesni_mb/{rte_pmd_aesni_version.map => rte_pmd_aesni_mb_version.map} (100%)
diff --git a/drivers/crypto/aesni_mb/Makefile b/drivers/crypto/aesni_mb/Makefile
index 611d4123b..e094178ce 100644
--- a/drivers/crypto/aesni_mb/Makefile
+++ b/drivers/crypto/aesni_mb/Makefile
@@ -47,7 +47,7 @@ CFLAGS += $(WERROR_FLAGS)
LIBABIVER := 1
# versioning export map
-EXPORT_MAP := rte_pmd_aesni_version.map
+EXPORT_MAP := rte_pmd_aesni_mb_version.map
# external library dependencies
CFLAGS += -I$(AESNI_MULTI_BUFFER_LIB_PATH)
diff --git a/drivers/crypto/aesni_mb/rte_pmd_aesni_version.map b/drivers/crypto/aesni_mb/rte_pmd_aesni_mb_version.map
similarity index 100%
rename from drivers/crypto/aesni_mb/rte_pmd_aesni_version.map
rename to drivers/crypto/aesni_mb/rte_pmd_aesni_mb_version.map
--
2.13.5
next prev parent reply other threads:[~2017-09-14 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 16:02 [dpdk-dev] [PATCH 0/2] have crypto drivers use a standard map file name format Bruce Richardson
2017-09-14 16:02 ` Bruce Richardson [this message]
2017-09-14 16:02 ` [dpdk-dev] [PATCH 2/2] crypto/armv8: rename map file to standard name Bruce Richardson
2017-09-18 9:35 ` [dpdk-dev] [PATCH 0/2] have crypto drivers use a standard map file name format Zhang, Roy Fan
2017-09-21 8:32 ` 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=20170914160214.94767-2-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pablo.de.lara.guarch@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).