From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-block@nongnu.org, armbru@redhat.com, mreitz@redhat.com,
pbonzini@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH] nbd/client: add x-block-status hack for testing server
Date: Thu, 21 Jun 2018 10:09:52 -0500 [thread overview]
Message-ID: <12d4807d-7999-1a0c-c5bf-1364e90546bb@redhat.com> (raw)
In-Reply-To: <152955990402.819.15911298646581883918@d39dc562802a>
On 06/21/2018 12:45 AM, no-reply@patchew.org wrote:
> Hi,
>
> This series failed build test on s390x host. Please find the details below.
>
> Type: series
> Message-id: 20180621032539.134944-1-eblake@redhat.com
> Subject: [Qemu-devel] [PATCH] nbd/client: add x-block-status hack for testing server
> CC block/nfs.o
> /var/tmp/patchew-tester-tmp-3490cfwt/src/nbd/server.c: In function ‘nbd_trip’:
> /var/tmp/patchew-tester-tmp-3490cfwt/src/nbd/server.c:1979:19: error: ‘end’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> *length = end - offset;
> ~~~~^~~~~~~~
That bug (rather, a gcc false-positive solved by adding an assertion
rather than an initialization) was in the 'Based-on' prerequisite
patches rather than this one. Here's hoping that patchew will retry
when I point to the v2 pull request (oh, and how does patchew handle a
v2 pull request that intentionally only sent the patches that differed
from v1):
Based-on:
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg06233.html
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-06-21 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 3:25 [Qemu-devel] [PATCH] nbd/client: add x-block-status hack for testing server Eric Blake
2018-06-21 5:45 ` no-reply
2018-06-21 15:09 ` Eric Blake [this message]
2018-06-21 5:53 ` no-reply
2018-06-29 15:53 ` Eric Blake
2018-06-25 13:50 ` Max Reitz
2018-06-25 17:12 ` John Snow
2018-06-29 10:01 ` Vladimir Sementsov-Ogievskiy
2018-06-29 15:55 ` Eric Blake
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=12d4807d-7999-1a0c-c5bf-1364e90546bb@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).