From: Markus Armbruster <armbru@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: qemu-devel@nongnu.org, chao.p.peng@intel.com, david@redhat.com,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3 1/5] virtio-mem: Fix definition of VirtIOMEMClass
Date: Thu, 05 Jun 2025 12:57:52 +0200 [thread overview]
Message-ID: <87cybiihfz.fsf@pond.sub.org> (raw)
In-Reply-To: <20250605102311.148171-2-zhenzhong.duan@intel.com> (Zhenzhong Duan's message of "Thu, 5 Jun 2025 18:23:07 +0800")
Zhenzhong Duan <zhenzhong.duan@intel.com> writes:
> Parent of VirtIOMEMClass is VirtioDeviceClass rather than VirtIODevice.
>
> Fixes: 910b25766b33 ("virtio-mem: Paravirtualized memory hot(un)plug")
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/hw/virtio/virtio-mem.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/hw/virtio/virtio-mem.h b/include/hw/virtio/virtio-mem.h
> index bc4f787772..e0ab31b45a 100644
> --- a/include/hw/virtio/virtio-mem.h
> +++ b/include/hw/virtio/virtio-mem.h
> @@ -134,7 +134,7 @@ struct VirtioMemSystemReset {
>
> struct VirtIOMEMClass {
> /* private */
> - VirtIODevice parent;
> + VirtioDeviceClass parent_class;
>
> /* public */
> void (*fill_device_info)(const VirtIOMEM *vmen, VirtioMEMDeviceInfo *vi);
*Ouch*
I guess this isn't catastrophic only because sizeof(VirtIODevice) >
sizeof(VirtioDeviceClass). Suggest to mention that in the commit
message.
Out of scope for this patch, but I'd really, really appreciate more
consistent spelling of VirtIO.
next prev parent reply other threads:[~2025-06-05 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 10:23 [PATCH v3 0/5] Fix definition of classes with wrong parent Zhenzhong Duan
2025-06-05 10:23 ` [PATCH v3 1/5] virtio-mem: Fix definition of VirtIOMEMClass Zhenzhong Duan
2025-06-05 10:57 ` Markus Armbruster [this message]
2025-06-06 9:10 ` Duan, Zhenzhong
2025-06-05 10:23 ` [PATCH v3 2/5] virtio-pmem: Fix definition of VirtIOPMEMClass Zhenzhong Duan
2025-06-05 10:23 ` [PATCH v3 3/5] hw/gpio/aspeed: Fix definition of AspeedGPIOClass Zhenzhong Duan
2025-06-05 10:23 ` [PATCH v3 4/5] hw/char/sh_serial: Remove dummy definition of SH_SERIAL class Zhenzhong Duan
2025-06-05 10:23 ` [PATCH v3 5/5] hw/riscv/riscv-iommu: Remove definition of RISCVIOMMU[Pci|Sys]Class Zhenzhong Duan
2025-06-05 13:24 ` Daniel Henrique Barboza
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=87cybiihfz.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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.