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 0/2] have crypto drivers use a standard map file name format
Date: Thu, 14 Sep 2017 17:02:12 +0100 [thread overview]
Message-ID: <20170914160214.94767-1-bruce.richardson@intel.com> (raw)
rename some of the version.map files that don't match the standard naming
convention. For future meson build system, this will save us having to
specify for each driver what the filename of its map file is.
Bruce Richardson (2):
crypto/aesni_mb: rename map file to standard name
crypto/armv8: rename map file to standard name
drivers/crypto/aesni_mb/Makefile | 2 +-
.../{rte_pmd_aesni_version.map => rte_pmd_aesni_mb_version.map} | 0
drivers/crypto/armv8/Makefile | 2 +-
.../armv8/{rte_armv8_pmd_version.map => rte_pmd_armv8_version.map} | 0
4 files changed, 2 insertions(+), 2 deletions(-)
rename drivers/crypto/aesni_mb/{rte_pmd_aesni_version.map => rte_pmd_aesni_mb_version.map} (100%)
rename drivers/crypto/armv8/{rte_armv8_pmd_version.map => rte_pmd_armv8_version.map} (100%)
--
2.13.5
next 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 Bruce Richardson [this message]
2017-09-14 16:02 ` [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: rename map file to standard name Bruce Richardson
2017-09-14 16:02 ` [dpdk-dev] [PATCH 2/2] crypto/armv8: " 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-1-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).