From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Alessandro Ratti" <alessandro@0x65c.net>,
alessandro.ratti@gmail.com, alex.bennee@linaro.org,
mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] virtio: improve virtqueue mapping error messages
Date: Tue, 10 Mar 2026 12:52:35 +0100 [thread overview]
Message-ID: <874imnc35o.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA85zD1d=4xkXKFyefYjsj14DqpBDXrPbtfSfa0ry8raKw@mail.gmail.com> (Peter Maydell's message of "Tue, 10 Mar 2026 11:09:01 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 10 Mar 2026 at 11:03, Markus Armbruster <armbru@redhat.com> wrote:
>> Neither function is ideal. But in their current state, I *strongly*
>> prefer qdev_get_human_name(), because I hate having to decipher a QOM
>> path less than having to guess what kind of device this might be, then
>> figure out what format its .get_dev_path() uses.
>>
>> If someone posts a patch to fix the shortcomings of
>> qdev_get_printable_name() I outlined above, we can talk.
>
> How do you feel about the proposed unification of the two
> functions done in this patch?
>
> https://lore.kernel.org/qemu-devel/20260308160040.354186-2-alessandro@0x65c.net/
Thanks for the pointer, I'll reply there.
prev parent reply other threads:[~2026-03-10 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 12:46 [PATCH] virtio: improve virtqueue mapping error messages Alessandro Ratti
2025-09-23 12:46 ` Alessandro Ratti
2025-09-23 15:09 ` [PATCH v2] " Alessandro Ratti
2025-09-23 15:09 ` Alessandro Ratti
2025-09-23 16:17 ` Daniel P. Berrangé
2025-09-24 9:14 ` [PATCH v3] " Alessandro Ratti
2025-09-24 9:14 ` Alessandro Ratti
2025-09-24 9:34 ` Daniel P. Berrangé
2026-03-07 13:39 ` Peter Maydell
2026-03-07 14:37 ` Alessandro Ratti
2026-03-10 11:02 ` Markus Armbruster
2026-03-10 11:09 ` Peter Maydell
2026-03-10 11:52 ` 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=874imnc35o.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alessandro.ratti@gmail.com \
--cc=alessandro@0x65c.net \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@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 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.