From: Zhao Liu <zhao1.liu@intel.com>
To: Shaoqin Huang <shahuang@redhat.com>
Cc: qemu-arm@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Eric Auger" <eauger@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH v11 2/3] vfio: Move the TYPE_* to hw/vfio/types.h
Date: Thu, 17 Jul 2025 22:18:41 +0800 [thread overview]
Message-ID: <aHkGQWeqoFiMKMwN@intel.com> (raw)
In-Reply-To: <20250717100941.2230408-3-shahuang@redhat.com>
On Thu, Jul 17, 2025 at 06:09:40AM -0400, Shaoqin Huang wrote:
> Date: Thu, 17 Jul 2025 06:09:40 -0400
> From: Shaoqin Huang <shahuang@redhat.com>
> Subject: [PATCH v11 2/3] vfio: Move the TYPE_* to hw/vfio/types.h
>
> Move the TYPE_* to a new file hw/vfio/types.h because the
> TYPE_VFIO_PCI will be used in later patch, but directly include the
> hw/vfio/pci.h can cause some compilation error when cross build the
> windows version.
>
> The hw/vfio/types.h can be included to mitigate that problem.
>
> Signed-off-by: Shaoqin Huang <shahuang@redhat.com>
> ---
> hw/vfio/pci.h | 10 +---------
> hw/vfio/types.h | 21 +++++++++++++++++++++
> 2 files changed, 22 insertions(+), 9 deletions(-)
> create mode 100644 hw/vfio/types.h
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
next prev parent reply other threads:[~2025-07-17 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 10:09 [PATCH v11 0/3] ramfb: Add property to control if load the romfile Shaoqin Huang
2025-07-17 10:09 ` [PATCH v11 1/3] " Shaoqin Huang
2025-07-17 10:09 ` [PATCH v11 2/3] vfio: Move the TYPE_* to hw/vfio/types.h Shaoqin Huang
2025-07-17 14:18 ` Zhao Liu [this message]
2025-07-17 10:09 ` [PATCH v11 3/3] hw/i386: Add the ramfb romfile compatibility Shaoqin Huang
2025-07-17 15:19 ` Cédric Le Goater
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=aHkGQWeqoFiMKMwN@intel.com \
--to=zhao1.liu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eauger@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shahuang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.