From: Hanna Reitz <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: [PATCH 3/4] block: Print protocol-specific information
Date: Tue, 3 May 2022 16:55:28 +0200 [thread overview]
Message-ID: <20220503145529.37070-4-hreitz@redhat.com> (raw)
In-Reply-To: <20220503145529.37070-1-hreitz@redhat.com>
Make bdrv_image_info_dump() print protocol-specific information.
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
---
block/qapi.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/block/qapi.c b/block/qapi.c
index 293983cf82..169ea08f70 100644
--- a/block/qapi.c
+++ b/block/qapi.c
@@ -921,4 +921,9 @@ void bdrv_image_info_dump(ImageInfo *info)
bdrv_image_info_specific_dump(info->format_specific,
"Format specific information:\n");
}
+
+ if (info->has_protocol_specific) {
+ bdrv_image_info_specific_dump(info->protocol_specific,
+ "Protocol specific information:\n");
+ }
}
--
2.35.1
next prev parent reply other threads:[~2022-05-03 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:55 [PATCH 0/4] block/file: Show extent size in qemu-img info Hanna Reitz
2022-05-03 14:55 ` [PATCH 1/4] block: Improve empty format-specific info dump Hanna Reitz
2022-05-03 18:44 ` Eric Blake
2022-05-04 8:18 ` Kevin Wolf
2022-05-03 14:55 ` [PATCH 2/4] block: Add protocol-specific image info Hanna Reitz
2022-05-03 18:47 ` Eric Blake
2022-05-04 8:36 ` Kevin Wolf
2022-05-04 11:25 ` Hanna Reitz
2022-05-03 14:55 ` Hanna Reitz [this message]
2022-05-03 18:48 ` [PATCH 3/4] block: Print protocol-specific information Eric Blake
2022-05-03 14:55 ` [PATCH 4/4] block/file: Add file-specific image info Hanna Reitz
2022-05-03 18:50 ` Eric Blake
2022-05-04 7:10 ` Hanna Reitz
2022-05-04 8:46 ` Kevin Wolf
2022-05-04 11:26 ` Hanna Reitz
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=20220503145529.37070-4-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.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).