From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org, no-reply@patchew.org, vsementsov@virtuozzo.com
Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org,
armbru@redhat.com, nshirokovskiy@virtuozzo.com, den@openvz.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block latency histogram
Date: Fri, 9 Mar 2018 09:39:02 -0600 [thread overview]
Message-ID: <de8fcf92-eac6-902d-eafd-f53d1c935dc7@redhat.com> (raw)
In-Reply-To: <152060804669.1497.3662068304242069251@bdbb90650ae5>
On 03/09/2018 09:07 AM, no-reply@patchew.org wrote:
> Hi,
>
> This series failed build test on ppcbe host. Please find the details below.
>
> Type: series
> Message-id: 20180309144918.44975-1-vsementsov@virtuozzo.com
> Subject: [Qemu-devel] [PATCH v3 0/2] block latency histogram
> In file included from /var/tmp/patchew-tester-tmp-e2uf385_/src/include/block/block_int.h:27:0,
> from /var/tmp/patchew-tester-tmp-e2uf385_/src/stubs/blockdev-close-all-bdrv-states.c:2:
> /var/tmp/patchew-tester-tmp-e2uf385_/src/include/block/accounting.h:117:33: error: unknown type name ‘uint64List’
> uint64List *boundaries);
> ^
Probably as simple as forgetting to #include "qapi/qapi-builtin-types.h"
as part of the rebasing to the recent QAPI refactoring that landed in
commit 7fceeb19.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-09 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 14:49 [Qemu-devel] [PATCH v3 0/2] block latency histogram Vladimir Sementsov-Ogievskiy
2018-03-09 14:49 ` [Qemu-devel] [PATCH v3 1/2] block/accounting: introduce " Vladimir Sementsov-Ogievskiy
2018-03-09 14:49 ` [Qemu-devel] [PATCH v3 2/2] qapi: add block latency histogram interface Vladimir Sementsov-Ogievskiy
2018-03-09 15:07 ` [Qemu-devel] [PATCH v3 0/2] block latency histogram no-reply
2018-03-09 15:39 ` Eric Blake [this message]
2018-03-09 15:15 ` no-reply
2018-03-09 15:20 ` no-reply
2018-03-09 15:26 ` no-reply
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=de8fcf92-eac6-902d-eafd-f53d1c935dc7@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=no-reply@patchew.org \
--cc=nshirokovskiy@virtuozzo.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).