public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
	"Michael Roth" <michael.roth@amd.com>,
	devel@lists.libvirt.org
Subject: Re: [PATCH-for-11.0] qapi: Remove deprecated SchemaInfoEnumMember::values field
Date: Tue, 24 Mar 2026 08:19:16 +0100	[thread overview]
Message-ID: <87bjgdvgnf.fsf@pond.sub.org> (raw)
In-Reply-To: <acIpLpMOTCwKwDQt@angien.pipo.sk> (Peter Krempa's message of "Tue, 24 Mar 2026 07:03:26 +0100")

Peter Krempa <pkrempa@redhat.com> writes:

> On Mon, Mar 23, 2026 at 20:19:45 -0700, Pierrick Bouvier wrote:
>> On 3/23/26 8:21 AM, Philippe Mathieu-Daudé wrote:
>> > SchemaInfoEnumMember::values field has been deprecated for
>> > more than 5 years (see commit 75ecee72625 "qapi: Enable enum
>> > member introspection to show more than name"), it should be
>> > safe enough to remove.
>> > 
>> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> > ---
>> >   docs/about/deprecated.rst       |  6 ------
>> >   docs/about/removed-features.rst |  7 +++++++
>> >   qapi/introspect.json            | 12 +-----------
>> >   scripts/qapi/introspect.py      |  3 +--
>> >   4 files changed, 9 insertions(+), 19 deletions(-)
>> > 
>> 
>> By curiosity, is this patch goal is simply to remove a deprecated
>> feature/code, or does it unlock something beyond it?
>> No judgment here, that's a genuine question, and both are valid reasons!
>
> This patch also shaves off a nice 1.3k lines of duplicate data from the
> prettified reply from query-qmp-schema.
>
> (In libvirt we capture dumps of the schema which we use for internal
> testing as well as validation that the monitor command handlers and
> commandline generators (by proxy) don't use deprecated and or
> non-existent members.)
>
>> Looks good to me, to the limit of my qapi knowledge :).
>> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>
> On behalf of libvirt (and since I didn't look at the code at all; just
> at the output):
>
> ACKed-by: Peter Krempa <pkrempa@redhat.com>

Thank you, Peter!

Reviewed-by: Markus Armbruster <armbru@redhat.com>



      reply	other threads:[~2026-03-24  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 15:21 [PATCH-for-11.0] qapi: Remove deprecated SchemaInfoEnumMember::values field Philippe Mathieu-Daudé
2026-03-24  3:19 ` Pierrick Bouvier
2026-03-24  5:00   ` Philippe Mathieu-Daudé
2026-03-24  7:02     ` Markus Armbruster
2026-03-24  9:15       ` Daniel P. Berrangé
2026-03-24  6:03   ` Peter Krempa
2026-03-24  7:19     ` Markus Armbruster [this message]

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=87bjgdvgnf.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=eblake@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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