From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, eduardo@habkost.net, philmd@linaro.org
Subject: [PATCH 0/3] qdev: Fix "info qtree" to show links
Date: Wed, 22 Oct 2025 12:14:17 +0200 [thread overview]
Message-ID: <20251022101420.36059-1-armbru@redhat.com> (raw)
This is an alternative to Marc-André's "[PATCH] RFC: qdev: add legacy
properties only for those print()-able"
Message-ID: <20251015105419.2975542-1-marcandre.lureau@redhat.com>
Markus Armbruster (3):
qdev: Change PropertyInfo method print() to return malloc'ed string
qdev: Fix "info qtree" to show links
qdev: Legacy properties are now unused, drop
include/hw/qdev-properties.h | 2 +-
hw/core/qdev-properties-system.c | 7 ++---
hw/core/qdev-properties.c | 47 --------------------------------
system/qdev-monitor.c | 7 ++---
4 files changed, 7 insertions(+), 56 deletions(-)
--
2.49.0
next reply other threads:[~2025-10-22 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:14 Markus Armbruster [this message]
2025-10-22 10:14 ` [PATCH 1/3] qdev: Change PropertyInfo method print() to return malloc'ed string Markus Armbruster
2025-10-22 10:59 ` Marc-André Lureau
2025-10-22 14:08 ` Markus Armbruster
2025-10-22 10:14 ` [PATCH 2/3] qdev: Fix "info qtree" to show links Markus Armbruster
2025-10-22 11:00 ` Marc-André Lureau
2025-10-24 7:05 ` Paolo Bonzini
2025-10-28 10:33 ` Markus Armbruster
2025-10-28 10:59 ` Daniel P. Berrangé
2025-10-28 13:10 ` Paolo Bonzini
2025-10-28 11:04 ` Peter Maydell
2025-10-28 12:58 ` Paolo Bonzini
2025-10-22 10:14 ` [PATCH 3/3] qdev: Legacy properties are now unused, drop Markus Armbruster
2025-10-22 11:13 ` Marc-André Lureau
2025-10-22 12:12 ` Markus Armbruster
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=20251022101420.36059-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).