Received: from eggs.gnu.org ([208.118.235.92]:57018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USm2w-0008TX-1U for qemu-devel@nongnu.org; Thu, 18 Apr 2013 06:26:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1USm2s-0004jR-83 for qemu-devel@nongnu.org; Thu, 18 Apr 2013 06:26:29 -0400 Received: from mail-ea0-x22e.google.com ([2a00:1450:4013:c01::22e]:63511) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USm2r-0004iI-UC for qemu-devel@nongnu.org; Thu, 18 Apr 2013 06:26:26 -0400 Received: by mail-ea0-f174.google.com with SMTP id m14so1152323eaj.19 for ; Thu, 18 Apr 2013 03:26:25 -0700 (PDT) Date: Thu, 18 Apr 2013 12:26:19 +0200 From: "Edgar E. Iglesias" Message-ID: <20130418102619.GG4915@smtp.vpn> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v5 0/3] DTC as submodule List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: peter.crosthwaite@xilinx.com Cc: peter.maydell@linaro.org, aliguori@us.ibm.com, qemu-devel@nongnu.org, pbonzini@redhat.com On Thu, Apr 18, 2013 at 02:45:35PM +1000, peter.crosthwaite@xilinx.com wrote: > From: Peter Crosthwaite > > These two patches add and use dtc as a submodule as per the RFC: > > http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg05000.html > > There is a remaining action item to mandate libfdt for arm/microblaze and PPC > which is left as follow up work for after review of this series. > > Also fixed the configure to properly build pixman when cross compiling. > > changed since v4: > Use error_exit in configure > changed since v3: > Rebase against recent configure devls. > changed since v2: > Fixed P1 implementation (PMM review) > Fixed CC/AR/LD quoting issue P3 (PMM review) > Addressed PMM review > changed since v1: > Fixed cross compilation of submodules (new P1) > Fixed passing of ARFLAGS to dtc submake Acked-by: Edgar E. Iglesias CC: Anthony and Bonzini Shouldn't we in scripts/make_release have a stage that walks the submodules and makes sure to bootstrap autoconf so that we package release-tarballs with pre-generated configure scripts? IIUC, that is standard practice for autoconf tarball releases but I might be wrong. Best regards, Edgar