From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com,
frankja@linux.vnet.ibm.com, thuth@redhat.com, david@redhat.com,
agraf@suse.de, pasic@linux.vnet.ibm.com, qemu-s390x@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4] s390/ipl: fix ipl with -no-reboot
Date: Fri, 22 Jun 2018 15:47:08 +0200 [thread overview]
Message-ID: <20180622154708.37167025.cohuck@redhat.com> (raw)
In-Reply-To: <5df62baa-268b-2624-e9d7-42c521546d04@de.ibm.com>
On Fri, 22 Jun 2018 15:29:04 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 06/22/2018 03:22 PM, no-reply@patchew.org wrote:
> > Hi,
> >
> > This series failed docker-mingw@fedora build test. Please find the testing commands and
> > their output below. If you have Docker installed, you can probably reproduce it
> > locally.
> >
>
> [...]
>
> > CC os-win32.o
> > CC bt-host.o
> > CC bt-vhci.o
> > CC dma-helpers.o
> > CC vl.o
> > CC tpm.o
> > CC device_tree.o
> > /tmp/qemu-test/src/nbd/server.c: In function 'nbd_trip':
> > /tmp/qemu-test/src/nbd/server.c:1980:19: error: 'end' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> > *length = end - offset;
> > ~~~~^~~~~~~~
> > /tmp/qemu-test/src/nbd/server.c:1940:30: note: 'end' was declared here
> > uint64_t begin = offset, end;
> > ^~~
> > cc1: all warnings being treated as errors
>
> This seems unrelated to the patch?
>
Yes, the last few patches all failed with this error.
next prev parent reply other threads:[~2018-06-22 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 10:29 [Qemu-devel] [PATCH v4] s390/ipl: fix ipl with -no-reboot Christian Borntraeger
2018-06-22 12:12 ` Paolo Bonzini
2018-06-22 12:14 ` Halil Pasic
2018-06-22 13:22 ` no-reply
2018-06-22 13:29 ` Christian Borntraeger
2018-06-22 13:47 ` Cornelia Huck [this message]
2018-06-22 14:10 ` Eric Blake
2018-06-22 13:50 ` Cornelia Huck
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=20180622154708.37167025.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=famz@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@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).