From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com, kwolf@redhat.com, pbonzini@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3 0/5] coroutine: Clean up includes
Date: Wed, 21 Dec 2022 22:47:36 +0100 [thread overview]
Message-ID: <18f53ca6-3cd0-313c-8940-1f7d013eba87@linaro.org> (raw)
In-Reply-To: <20221221131435.3851212-1-armbru@redhat.com>
On 21/12/22 14:14, Markus Armbruster wrote:
> v3:
> * PATCH 4: Unnecessary hunks dropped
>
> v2:
> * Rebased
> * PATCH 4: Rewritten [Paolo]
> * PATCH 5: New
>
> Markus Armbruster (5):
> coroutine: Clean up superfluous inclusion of qemu/coroutine.h
> coroutine: Move coroutine_fn to qemu/osdep.h, trim includes
> coroutine: Clean up superfluous inclusion of qemu/lockable.h
> coroutine: Split qemu/coroutine-core.h off qemu/coroutine.h
> coroutine: Use Coroutine typedef name instead of structure tag
I had to add:
-- >8 --
diff --git a/hw/pci/pci-hmp-cmds.c b/hw/pci/pci-hmp-cmds.c
index fb7591d6ab..b09fce9377 100644
--- a/hw/pci/pci-hmp-cmds.c
+++ b/hw/pci/pci-hmp-cmds.c
@@ -15,6 +15,7 @@
#include "qemu/osdep.h"
#include "hw/pci/pci.h"
+#include "hw/pci/pci_device.h"
#include "monitor/hmp.h"
#include "monitor/monitor.h"
#include "pci-internal.h"
diff --git a/hw/virtio/virtio-qmp.c b/hw/virtio/virtio-qmp.c
index 8e7282658f..3d4497da99 100644
--- a/hw/virtio/virtio-qmp.c
+++ b/hw/virtio/virtio-qmp.c
@@ -11,6 +11,7 @@
#include "qemu/osdep.h"
#include "hw/virtio/virtio.h"
+#include "hw/virtio/vhost.h"
#include "virtio-qmp.h"
---
Otherwise I get:
../hw/pci/pci-hmp-cmds.c: In function ‘pcibus_dev_print’:
../hw/pci/pci-hmp-cmds.c:129:31: error: invalid use of incomplete
typedef ‘PCIDevice’
129 | int class = pci_get_word(d->config + PCI_CLASS_DEVICE);
| ^~
../hw/virtio/virtio-qmp.c:187:19: error:
‘VHOST_USER_F_PROTOCOL_FEATURES’ undeclared here (not in a function);
did you mean ‘VHOST_USER_PROTOCOL_F_RARP’?
187 | FEATURE_ENTRY(VHOST_USER_F_PROTOCOL_FEATURES, \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Maybe some recently merged change?
Otherwise:
Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2022-12-21 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 13:14 [PATCH v3 0/5] coroutine: Clean up includes Markus Armbruster
2022-12-21 13:14 ` [PATCH v3 1/5] coroutine: Clean up superfluous inclusion of qemu/coroutine.h Markus Armbruster
2022-12-21 13:14 ` [PATCH v3 2/5] coroutine: Move coroutine_fn to qemu/osdep.h, trim includes Markus Armbruster
2022-12-21 13:14 ` [PATCH v3 3/5] coroutine: Clean up superfluous inclusion of qemu/lockable.h Markus Armbruster
2022-12-21 13:14 ` [PATCH v3 4/5] coroutine: Split qemu/coroutine-core.h off qemu/coroutine.h Markus Armbruster
2022-12-22 8:01 ` Paolo Bonzini
2022-12-22 8:56 ` Markus Armbruster
2022-12-22 11:14 ` Paolo Bonzini
2022-12-21 13:14 ` [PATCH v3 5/5] coroutine: Use Coroutine typedef name instead of structure tag Markus Armbruster
2022-12-21 21:47 ` Philippe Mathieu-Daudé [this message]
2022-12-22 5:21 ` [PATCH v3 0/5] coroutine: Clean up includes Markus Armbruster
2022-12-22 7:09 ` Philippe Mathieu-Daudé
2022-12-22 10:02 ` Markus Armbruster
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=18f53ca6-3cd0-313c-8940-1f7d013eba87@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).