qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, eric.auger@redhat.com,
	peterx@redhat.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support
Date: Tue, 1 May 2018 11:05:51 -0600	[thread overview]
Message-ID: <20180501110551.55d88528@w520.home> (raw)
In-Reply-To: <152519378671.2439.1373788398394753477@71c20359a636>

On Tue, 1 May 2018 09:56:27 -0700 (PDT)
no-reply@patchew.org wrote:

> Hi,
> 
> This series failed docker-build@min-glib build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.
> 
> Type: series
> Message-id: 20180501162901.28940.1075.stgit@gimli.home
> Subject: [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support
> ...
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c: In function 'vfio_ioeventfd_exit':
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:300: error: storage size of 'vfio_ioeventfd' isn't known
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:309: error: 'VFIO_DEVICE_IOEVENTFD' undeclared (first use in this function)
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:309: error: (Each undeclared identifier is reported only once
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:309: error: for each function it appears in.)
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:300: warning: unused variable 'vfio_ioeventfd'
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c: In function 'vfio_ioeventfd_init':
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:384: error: storage size of 'vfio_ioeventfd' isn't known
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:394: error: 'VFIO_DEVICE_IOEVENTFD' undeclared (first use in this function)
> /tmp/qemu-test/src/hw/vfio/pci-quirks.c:384: warning: unused variable 'vfio_ioeventfd'

Fails to build because of header dependency noted in the cover letter,
expected.  Thanks,

Alex

  reply	other threads:[~2018-05-01 17:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 16:42 [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support Alex Williamson
2018-05-01 16:43 ` [Qemu-devel] [PATCH v2 1/4] vfio/quirks: Add common quirk alloc helper Alex Williamson
2018-05-01 16:43 ` [Qemu-devel] [PATCH v2 2/4] vfio/quirks: Add quirk reset callback Alex Williamson
2018-05-01 16:43 ` [Qemu-devel] [PATCH v2 3/4] vfio/quirks: ioeventfd quirk acceleration Alex Williamson
2018-05-03  3:36   ` Peter Xu
2018-05-03  4:20     ` Alex Williamson
2018-05-03 14:33   ` Auger Eric
2018-05-03 14:48     ` Alex Williamson
2018-05-01 16:43 ` [Qemu-devel] [PATCH v2 4/4] vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly Alex Williamson
2018-05-03  4:56   ` Peter Xu
2018-05-03 16:29     ` Alex Williamson
2018-05-04  2:16       ` Peter Xu
2018-05-04  7:38       ` Auger Eric
2018-05-03 15:20   ` Auger Eric
2018-05-03 16:30     ` Alex Williamson
2018-05-01 16:56 ` [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support no-reply
2018-05-01 17:05   ` Alex Williamson [this message]
2018-05-01 16:56 ` 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=20180501110551.55d88528@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=famz@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=peterx@redhat.com \
    --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).