From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 2D156F94 for ; Thu, 31 Aug 2017 17:26:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D255020CDD; Thu, 31 Aug 2017 11:26:15 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 31 Aug 2017 11:26:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=VXpRAb5QWzc6nKr EsbHjS7DVh/YBKMZkaC1EmXR4CaY=; b=hZr+gycXuWIv5XU8VMHYpyHQVTgIeno gXhRu/eoWcrek/0Q/pKIpKwXTh46AuS1oXyA5g7m8mjCpPqkulVdmm/Br/Lsg++6 Lef7rICJ/2bjRwScp7m1PgNS6OhcuwT3/5b1RHDXhd/j0k5Kyhit15G3IueVpfy7 vpoRAj2biNMU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=VXpRAb5QWzc6nKrEsbHjS7DVh/YBKMZkaC1EmXR4CaY=; b=Rwti2WnV FghsckmPCB0gMJbnj/WepARATFBIeq0+zdLzzVaCq0I7dAn2v1FHf4J0/S6hgiCY 4xdPS+ftZJ5tqL4RoDhSy8VrwTAwt4PIC1lwGmE2JW/Y8ao17ya1gNr8AF7oiOfV kRwyQTQoun4TK83Id+i7z0p2jeKa1/lMkbZhIpbQM6j70P90PawBBsFGWhZoMLt1 78Lwwy6438/L4jy/tQqByG6fULbreMpxh7bVsSTaWjIXZlvIyv94xwyL3dYGD+ie 2/ZOjgXQ23iaAmBUNtikWX5ASyAirLEcJUGKAnZAV5zFibMm7x6KiowUoQp3lobX VIhcQ53Q9aCG8Q== X-ME-Sender: X-Sasl-enc: SzBoEqcZmCOhd2cBPFLlrudnA2LMHxS4p7Ae+3zyHDSA 1504193175 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 93FE624767; Thu, 31 Aug 2017 11:26:15 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: konstantin.ananyev@intel.com, ferruh.yigit@intel.com, john.griffin@intel.com, fiona.trahe@intel.com, dev@dpdk.org Date: Thu, 31 Aug 2017 17:26:14 +0200 Message-ID: <3102255.qYLVZAutG1@xps> In-Reply-To: <20170831143457.GB7984@bricha3-MOBL3.ger.corp.intel.com> References: <20170831134244.35215-1-bruce.richardson@intel.com> <0361277a-6b33-8299-c1cb-a4c8bffc1d06@intel.com> <20170831143457.GB7984@bricha3-MOBL3.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/4] minor cleanup of filenames and deps 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, 31 Aug 2017 15:26:16 -0000 31/08/2017 16:34, Bruce Richardson: > On Thu, Aug 31, 2017 at 03:15:05PM +0100, Ferruh Yigit wrote: > > On 8/31/2017 2:42 PM, Bruce Richardson wrote: > > > While working on a build system replacement, I find a number of small > > > inconsistencies and minor issues with our current code, which, if fixed > > > would make it simplier to generalize DPDK build rules. Main set of changes > > > is to have the name of the version.map file for libs/drivers consistent > > > with the component name - especially in cases where the directory name and > > > component name differ slightly. > > > > > > NOTE: this patchset is not meant to cover all instances of filename cleanup, > > > it just covers the instances I've encountered thus far. Any other instances > > > can be fixed as necessary as drivers are being "mesonified" [1]. > > > > > > [1] http://www.gocomics.com/calvinandhobbes/1993/01/25 :-) > > > > > > Bruce Richardson (4): > > > ip_frag: change map filename to standardized value > > > net/ring: change map filename to standardized value > > > ether: rename version file to match library name > > > crypto/qat: remove dependency on ether library > > > > Series Reviewed-by: Ferruh Yigit > > Hi Thomas, > > while these patches are mainly to enable my meson build work, it would > be easier for me, I think, if they could be applied on the main tree > directly, rather than going through the "next" tree. That way the > content on my tree is solely build-system related. > > Is that ok with you? Yes OK