From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, Chrysostomos Nanakos <chris@include.gr>
Subject: Re: [Qemu-devel] [PATCH for-2.9] block/archipelago: Make it compile
Date: Wed, 8 Mar 2017 19:32:53 +0100 [thread overview]
Message-ID: <cf2a46ae-afd3-58ea-7a1b-2de4e1d89a16@redhat.com> (raw)
In-Reply-To: <91dff396-0e71-cb32-8353-edc4b644d5af@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On 08.03.2017 19:28, Eric Blake wrote:
> On 03/08/2017 12:25 PM, Eric Blake wrote:
>> On 03/08/2017 12:18 PM, Max Reitz wrote:
>>> In order to use error_setg() and similar functions, we need to include
>>> qapi/error.h.
>>>
>>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>>> ---
>>> block/archipelago.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>
>> Does this mean our automated buildbots aren't building archipelago by
>> default?
>>
>
> Oh, I meant to add:
>
> Should probably mention that it was commit da34e65 that introduced the
> problem (if I'm right?). Does that mean we have not been compiling
> archipelago.c since Mar 2016?
At least here on my machine it does indeed compile before that commit
and fails afterwards. So, yes, maybe we actually have not. :-)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-03-08 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 18:18 [Qemu-devel] [PATCH for-2.9] block/archipelago: Make it compile Max Reitz
2017-03-08 18:25 ` Eric Blake
2017-03-08 18:27 ` Max Reitz
2017-03-08 18:28 ` Eric Blake
2017-03-08 18:32 ` Max Reitz [this message]
2017-03-08 18:46 ` Kevin Wolf
2017-03-08 19:33 ` Eric Blake
2017-03-08 18:38 ` Philippe Mathieu-Daudé
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=cf2a46ae-afd3-58ea-7a1b-2de4e1d89a16@redhat.com \
--to=mreitz@redhat.com \
--cc=chris@include.gr \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).