From: Cornelia Huck <cohuck@redhat.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, "Thomas Weißschuh" <thomas@t-8ch.de>
Subject: Re: [PATCH v4 2/4] hw/misc/pvpanic: centralize definition of supported events
Date: Fri, 12 Jan 2024 10:45:57 +0100 [thread overview]
Message-ID: <87h6jiopey.fsf@redhat.com> (raw)
In-Reply-To: <20240107-pvpanic-shutdown-v4-2-81500a7e4081@t-8ch.de>
On Sun, Jan 07 2024, Thomas Weißschuh <thomas@t-8ch.de> wrote:
> The different components of pvpanic duplicate the list of supported
> events. Move it to the shared header file to minimize changes when new
> events are added.
>
> Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
> ---
> hw/misc/pvpanic-isa.c | 2 +-
> hw/misc/pvpanic-pci.c | 2 +-
> hw/misc/pvpanic.c | 2 +-
> include/hw/misc/pvpanic.h | 1 +
> 4 files changed, 4 insertions(+), 3 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2024-01-12 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 14:05 [PATCH v4 0/4] hw/misc/pvpanic: add support for normal shutdowns Thomas Weißschuh
2024-01-07 14:05 ` [PATCH v4 1/4] linux-headers: drop pvpanic.h Thomas Weißschuh
2024-01-08 11:09 ` Thomas Huth
2024-01-12 9:44 ` Cornelia Huck
2024-01-07 14:05 ` [PATCH v4 2/4] hw/misc/pvpanic: centralize definition of supported events Thomas Weißschuh
2024-01-08 11:10 ` Thomas Huth
2024-01-12 9:45 ` Cornelia Huck [this message]
2024-01-07 14:05 ` [PATCH v4 3/4] tests/qtest/pvpanic: use centralized " Thomas Weißschuh
2024-01-12 9:47 ` Cornelia Huck
2024-01-07 14:05 ` [PATCH v4 4/4] hw/misc/pvpanic: add support for normal shutdowns Thomas Weißschuh
2024-01-12 9:51 ` Cornelia Huck
2024-01-26 18:47 ` Alejandro Jimenez
2024-01-26 21:52 ` Thomas Weißschuh
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=87h6jiopey.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
--cc=thuth@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).