All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Alessandro Ratti <alessandro@0x65c.net>
Cc: qemu-devel@nongnu.org,  peter.maydell@linaro.org,
	 berrange@redhat.com, mst@redhat.com,  pbonzini@redhat.com
Subject: Re: [PATCH v3 1/3] hw/qdev: Clarify fallback order in qdev_get_printable_name()
Date: Fri, 27 Mar 2026 14:56:15 +0100	[thread overview]
Message-ID: <87jyux4br4.fsf@pond.sub.org> (raw)
In-Reply-To: <20260321100405.1525059-2-alessandro@0x65c.net> (Alessandro Ratti's message of "Sat, 21 Mar 2026 11:04:03 +0100")

Alessandro Ratti <alessandro@0x65c.net> writes:

> Replace the uninformative "<unknown device>" final fallback with the
> canonical QOM path (e.g. /machine/peripheral-anon/device[0]).
>
> Also clean up comments to accurately describe qdev_get_dev_path()
> behavior, drop an unnecessary comment on the dev->id check, and rename
> the @vdev parameter to @dev for consistency with surrounding code.
>
> Update the doc comment in qdev.h to reflect the new fallback chain.
>
> Signed-off-by: Alessandro Ratti <alessandro@0x65c.net>

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



  reply	other threads:[~2026-03-27 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 10:04 [PATCH v3 0/3] hw/qdev: Consolidate qdev_get_human_name() and qdev_get_printable_name() Alessandro Ratti
2026-03-21 10:04 ` [PATCH v3 1/3] hw/qdev: Clarify fallback order in qdev_get_printable_name() Alessandro Ratti
2026-03-27 13:56   ` Markus Armbruster [this message]
2026-03-21 10:04 ` [PATCH v3 2/3] hw/qdev: Prefix bus type in qdev_get_printable_name() device paths Alessandro Ratti
2026-03-27 13:56   ` Markus Armbruster
2026-03-21 10:04 ` [PATCH v3 3/3] hw/qdev: Consolidate qdev_get_printable_name() into qdev_get_human_name() Alessandro Ratti
2026-03-27 13:57   ` Markus Armbruster
2026-04-30  9:07 ` [PATCH v3 0/3] hw/qdev: Consolidate qdev_get_human_name() and qdev_get_printable_name() Paolo Bonzini

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=87jyux4br4.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alessandro@0x65c.net \
    --cc=berrange@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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.