From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 54B521B486 for ; Thu, 31 Jan 2019 21:43:21 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 87D32A786E; Thu, 31 Jan 2019 20:43:20 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.61]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 907475B6A7; Thu, 31 Jan 2019 20:43:19 +0000 (UTC) From: Aaron Conole To: Bruce Richardson Cc: Michael Santana , dev@dpdk.org, Honnappa Nagarahalli , Thomas Monjalon References: <20190123220714.20763-1-msantana@redhat.com> <20190130221602.13866-1-msantana@redhat.com> <20190130221602.13866-3-msantana@redhat.com> <20190131092510.GC122080@bricha3-MOBL.ger.corp.intel.com> <20190131203229.GA254920@bricha3-MOBL.ger.corp.intel.com> Date: Thu, 31 Jan 2019 15:43:18 -0500 In-Reply-To: <20190131203229.GA254920@bricha3-MOBL.ger.corp.intel.com> (Bruce Richardson's message of "Thu, 31 Jan 2019 20:32:29 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 31 Jan 2019 20:43:20 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v2 2/2] ci: Introduce travis builds for github repositories 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 Jan 2019 20:43:21 -0000 Bruce Richardson writes: > On Thu, Jan 31, 2019 at 11:43:19AM -0500, Aaron Conole wrote: >> Bruce Richardson writes: >> > >> > >> > This looks very similar to the "config/arm/arm64_armv8_linuxapp_gcc" file. >> > I suggest that file be used instead of adding a new one. >> >> Agreed, we can drop this. I completely missed the configurations in >> that directory. >> > Yes, they probably aren't stored in a great location for discoverability. > We should look to move them to a better place in the repo. Suggestions > welcome! It's probably okay to leave them there. The build guides do make reference to them (I just missed it, my fault). > /Bruce