From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 44F1D9FE for ; Tue, 12 Sep 2017 21:19:53 +0200 (CEST) Received: from [2606:a000:111b:41f4:2201:d2d7:1fb:4ffb] (helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1drqie-0002UA-28; Tue, 12 Sep 2017 15:19:48 -0400 Date: Tue, 12 Sep 2017 15:19:35 -0400 From: Neil Horman To: "Wiles, Keith" Cc: "Richardson, Bruce" , "dev@dpdk.org" , "luca.boccassi@gmail.com" , "Van Haaren, Harry" Message-ID: <20170912191935.GA2849@hmswarspite.think-freely.org> References: <20170901100416.80264-1-bruce.richardson@intel.com> <20170912103809.140473-1-bruce.richardson@intel.com> <384F7233-089F-4D6D-98C8-93FC26166254@intel.com> <20170912132416.GA24040@bricha3-MOBL3.ger.corp.intel.com> <0B16187C-2403-46D9-BCA6-A20659DF3CB8@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0B16187C-2403-46D9-BCA6-A20659DF3CB8@intel.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-Spam-Score: -2.9 (--) X-Spam-Status: No Subject: Re: [dpdk-dev] [PATCH v2 00/17] build DPDK libs and some drivers with meson/ninja 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: Tue, 12 Sep 2017 19:19:53 -0000 On Tue, Sep 12, 2017 at 01:26:09PM +0000, Wiles, Keith wrote: > > > On Sep 12, 2017, at 8:24 AM, Richardson, Bruce wrote: > > > > On Tue, Sep 12, 2017 at 02:21:22PM +0100, Wiles, Keith wrote: > >> > >>> On Sep 12, 2017, at 5:37 AM, Bruce Richardson wrote: > >>> > >>> V2 changes: > >>> * fixed copyright notices, updated 2016 to 2017 > >>> * removed dependency on kconfig file in kernel build tree > >>> * marked pmdinfogen as a "native" binary, in preparation for future cross- > >>> compilation work > >>> * added in additional warning flags for compatibility with existing system > >>> —— > >> > >> > >>> Once reviewed and tested a bit, I hope to apply this set - or a new > >>> revision of it - to the build-next tree, to serve as a baseline for others > >>> to use and to add the missing functionality to. > >> > >> I would really like to see these patches in a build-next tree as it is much easier to work with and help with changes then patches on the master. > >> > >> When can we have a build-next tree created? > >> > > Tree already exists. I'm just waiting on a bit more review and ideally > > an ack before I apply this set there. > > Not sure what you are waiting for as an ack is not going to make much of a difference IMO :-) > Why would an ACK not make any difference? Are you suggesting that using this is a forgone conclusion? Neil > > > > http://dpdk.org/browse/draft/dpdk-next-build/ > > > > /Bruce > > Regards, > Keith >