From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Jakowski, Andrzej" <andrzej.jakowski@intel.com>
Subject: Re: [PATCH for QEMU] hw/vfio: Add VMD Passthrough Quirk
Date: Wed, 22 Apr 2020 22:17:56 +0000 [thread overview]
Message-ID: <48e2ef3f6f843d533e4f3cdb83da9be5184768e6.camel@intel.com> (raw)
In-Reply-To: <158759136841.3922.4821101148440128786@39012742ff91>
On Wed, 2020-04-22 at 14:36 -0700, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20200422171305.10923-1-jonathan.derrick@intel.com/
>
>
>
> Hi,
>
> This series failed the asan build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
> export ARCH=x86_64
> make docker-image-fedora V=1 NETWORK=1
> time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
> === TEST SCRIPT END ===
>
> CC qemu-io-cmds.o
> CC replication.o
> In file included from hw/vfio/trace.c:5:
> /tmp/qemu-test/build/hw/vfio/trace.h:2348:120: error: expected ')'
> qemu_log("%d@%zu.%06zu:vfio_pci_vmd_quirk_shadow_regs " "%s membar1_phys=0x%"PRIx64" membar2_phys=0x%"PRIx64" "\n",
> ^
>
It's the extra " at the end, which will be fixed in v2
Thanks for the sanity check
next prev parent reply other threads:[~2020-04-22 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 17:13 [PATCH for QEMU] hw/vfio: Add VMD Passthrough Quirk Jon Derrick
2020-04-22 17:13 ` [PATCH 1/1] pci: vmd: Use Shadow MEMBAR registers for QEMU/KVM guests Jon Derrick
2020-04-22 21:08 ` [PATCH for QEMU] hw/vfio: Add VMD Passthrough Quirk Andrzej Jakowski
2020-04-22 21:36 ` no-reply
2020-04-22 22:17 ` Derrick, Jonathan [this message]
2020-04-22 21:39 ` 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=48e2ef3f6f843d533e4f3cdb83da9be5184768e6.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=andrzej.jakowski@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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).