From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v2 2/2] ci: Introduce travis builds for
	github repositories
Date: Thu, 31 Jan 2019 15:43:18 -0500
Message-ID: <f7t1s4ssgm1.fsf@dhcp-25.97.bos.redhat.com>
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>
 <f7tva24srq0.fsf@dhcp-25.97.bos.redhat.com>
 <20190131203229.GA254920@bricha3-MOBL.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: Michael Santana <msantana@redhat.com>, dev@dpdk.org,
 Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
 Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 54B521B486
 for <dev@dpdk.org>; Thu, 31 Jan 2019 21:43:21 +0100 (CET)
In-Reply-To: <20190131203229.GA254920@bricha3-MOBL.ger.corp.intel.com> (Bruce
 Richardson's message of "Thu, 31 Jan 2019 20:32:29 +0000")
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Bruce Richardson <bruce.richardson@intel.com> writes:

> On Thu, Jan 31, 2019 at 11:43:19AM -0500, Aaron Conole wrote:
>> Bruce Richardson <bruce.richardson@intel.com> writes:
>> 
> <snip>
>> >
>> > 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