From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 547741041 for ; Thu, 14 Sep 2017 18:02:47 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Sep 2017 09:02:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,393,1500966000"; d="scan'208";a="135381374" Received: from silpixa00399126.ir.intel.com (HELO silpixa00399126.ger.corp.intel.com) ([10.237.223.223]) by orsmga002.jf.intel.com with ESMTP; 14 Sep 2017 09:02:20 -0700 From: Bruce Richardson To: pablo.de.lara.guarch@intel.com, declan.doherty@intel.com, jerin.jacob@caviumnetworks.com Cc: dev@dpdk.org, Bruce Richardson Date: Thu, 14 Sep 2017 17:02:12 +0100 Message-Id: <20170914160214.94767-1-bruce.richardson@intel.com> X-Mailer: git-send-email 2.13.5 Subject: [dpdk-dev] [PATCH 0/2] have crypto drivers use a standard map file name format X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2017 16:02:48 -0000 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