From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PULL v3 00/15] Tracing patches
Date: Fri, 13 Nov 2015 18:03:12 +0100 [thread overview]
Message-ID: <20151113170312.GA12172@toto> (raw)
In-Reply-To: <CAFEAcA9Fy8K44i-Vuu-BvKcjUq2oeJpj85JLPkEwuA4SSCmSTA@mail.gmail.com>
On Fri, Nov 13, 2015 at 11:28:41AM +0000, Peter Maydell wrote:
> On 13 November 2015 at 10:30, Peter Maydell <peter.maydell@linaro.org> 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
next prev parent reply other threads:[~2015-11-13 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 7:58 [Qemu-devel] [PULL v3 00/15] Tracing patches Stefan Hajnoczi
2015-11-13 10:30 ` Peter Maydell
2015-11-13 10:44 ` Stefan Hajnoczi
2015-12-21 5:53 ` Denis V. Lunev
2016-01-08 2:49 ` Stefan Hajnoczi
2015-11-13 11:28 ` Peter Maydell
2015-11-13 17:03 ` Edgar E. Iglesias [this message]
2015-11-20 12:15 ` Alistair Francis
2015-11-13 11:52 ` Paolo Bonzini
2016-01-04 8:00 ` Denis V. Lunev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151113170312.GA12172@toto \
--to=edgar.iglesias@gmail.com \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaite.peter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).