From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxHkv-0000xC-Tb for qemu-devel@nongnu.org; Fri, 13 Nov 2015 12:03:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxHkq-0003iz-Ud for qemu-devel@nongnu.org; Fri, 13 Nov 2015 12:03:21 -0500 Received: from mail-pa0-x236.google.com ([2607:f8b0:400e:c03::236]:34826) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxHkq-0003iX-QJ for qemu-devel@nongnu.org; Fri, 13 Nov 2015 12:03:16 -0500 Received: by pasz6 with SMTP id z6so108848969pas.2 for ; Fri, 13 Nov 2015 09:03:16 -0800 (PST) Date: Fri, 13 Nov 2015 18:03:12 +0100 From: "Edgar E. Iglesias" Message-ID: <20151113170312.GA12172@toto> References: <1447401507-6319-1-git-send-email-stefanha@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL v3 00/15] Tracing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Alistair Francis , QEMU Developers , Stefan Hajnoczi , Peter Crosthwaite On Fri, Nov 13, 2015 at 11:28:41AM +0000, Peter Maydell wrote: > On 13 November 2015 at 10:30, Peter Maydell wrote: > > I also now get a handful of extra warnings in the 'make check' output: > > > > /aarch64/qom/xilinx-zynq-a9: OK > > /aarch64/qom/xlnx-ep108: > > WARNING: RAM size 8000000 is small for EP108OK > > /aarch64/qom/vexpress-a9: OK > > > > (note the missing newline...) > > > > TEST: tests/qom-test... (pid=19738) > > /microblaze/qom/none: OK > > /microblaze/qom/petalogix-s3adsp1800: > > Invalid MicroBlaze version number: (null) > > OK > > /microblaze/qom/petalogix-ml605: > > Invalid MicroBlaze version number: (null) > > OK > > Peter/Alistair/Edgar: this patchset of Stefan's has now been deferred > until 2.6, but you might want to look into the log warning issues > it exposed (the missing newline, attempt to print NULL, and maybe > whether the warnings should really be printed for a simple attempt > to start the board with no arguments). > Thanks, I've posted patches to fix the MicroBlaze warings on the list. I don't know what the inention was with the E1P08 warning.. IMO we can remove it... Cheers, Edgar