From: Magnus Kulke <magnuskulke@linux.microsoft.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Shameer Kolothum <skolothumtho@nvidia.com>
Subject: Re: [PATCH] include/hw/hyperv: Remove unused 'struct mshv_vp_registers' definition
Date: Mon, 12 Jan 2026 16:31:48 +0100 [thread overview]
Message-ID: <aWUT5GVD97KXXwIj@example.com> (raw)
In-Reply-To: <20260108185012.2568277-1-clg@redhat.com>
Reviewed-by: Magnus Kulke <magnuskulke@linux.microsoft.com>
Thanks, looks good to me.
On Thu, Jan 08, 2026 at 07:50:12PM +0100, Cédric Le Goater wrote:
> The 'struct mshv_vp_registers' definition in hvgdk_mini.h is unused in
> QEMU and conflicts with the canonical definition in
> linux-headers/linux/mshv.h.
>
> Remove the duplicate definition to avoid build conflicts when the Linux
> headers are updated.
>
> Cc: Magnus Kulke <magnuskulke@linux.microsoft.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
> include/hw/hyperv/hvgdk_mini.h | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/include/hw/hyperv/hvgdk_mini.h b/include/hw/hyperv/hvgdk_mini.h
> index d89315f5452fd565469bbfc98cacb226b71da13f..cb52cc9de283bbe4201357127c2eb1b0b37e4cab 100644
> --- a/include/hw/hyperv/hvgdk_mini.h
> +++ b/include/hw/hyperv/hvgdk_mini.h
> @@ -450,13 +450,6 @@ typedef struct hv_input_set_vp_registers {
> struct hv_register_assoc elements[];
> } hv_input_set_vp_registers;
>
> -#define MSHV_VP_MAX_REGISTERS 128
> -
> -struct mshv_vp_registers {
> - int count; /* at most MSHV_VP_MAX_REGISTERS */
> - struct hv_register_assoc *regs;
> -};
> -
> union hv_interrupt_control {
> uint64_t as_uint64;
> struct {
> --
> 2.52.0
next prev parent reply other threads:[~2026-01-12 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 18:50 [PATCH] include/hw/hyperv: Remove unused 'struct mshv_vp_registers' definition Cédric Le Goater
2026-01-12 15:31 ` Magnus Kulke [this message]
2026-01-13 7:32 ` 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=aWUT5GVD97KXXwIj@example.com \
--to=magnuskulke@linux.microsoft.com \
--cc=clg@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.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.