From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
devel@lists.libvirt.org,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Mads Ynddal" <mads@ynddal.dk>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Igor Mammedov" <imammedo@redhat.com>,
"Greg Kurz" <groug@kaod.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
qemu-ppc@nongnu.org, "Eric Blake" <eblake@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Ani Sinha" <anisinha@redhat.com>
Subject: Re: [PATCH 0/2] qapi: Remove deprecated events
Date: Mon, 03 Jun 2024 13:22:54 +0200 [thread overview]
Message-ID: <875xuqtgmp.fsf@pond.sub.org> (raw)
In-Reply-To: <20240530071548.20074-1-philmd@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Thu, 30 May 2024 09:15:46 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> Remove MEM_UNPLUG_ERROR and 'vcpu' field in TRACE events,
> all deprecated since long enough.
Thank you!
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2024-06-03 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 7:15 [PATCH 0/2] qapi: Remove deprecated events Philippe Mathieu-Daudé
2024-05-30 7:15 ` [PATCH 1/2] hw/acpi: Remove the deprecated QAPI MEM_UNPLUG_ERROR event Philippe Mathieu-Daudé
2024-05-30 8:23 ` Harsh Prateek Bora
2024-05-30 7:15 ` [PATCH 2/2] trace: Remove deprecated 'vcpu' field from QMP trace events Philippe Mathieu-Daudé
2024-06-02 22:03 ` [PATCH 0/2] qapi: Remove deprecated events Michael S. Tsirkin
2024-06-03 11:22 ` Markus Armbruster [this message]
2024-06-03 12:45 ` Philippe Mathieu-Daudé
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=875xuqtgmp.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anisinha@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=devel@lists.libvirt.org \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=imammedo@redhat.com \
--cc=mads@ynddal.dk \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangyanan55@huawei.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).