From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: [PATCH 0/3] block: remove separate bdrv_file_open callback
Date: Thu, 9 Mar 2023 09:50:48 +0100 [thread overview]
Message-ID: <20230309085051.308664-1-pbonzini@redhat.com> (raw)
The value of the bdrv_file_open is sometimes checked to distinguish
protocol and format drivers, but apart from that there is no difference
between bdrv_file_open and bdrv_open.
However, they can all be distinguished by the non-NULL .protocol_name
member. Change the checks to use .protocol_name instead of .bdrv_file_open,
and unify the two callbacks.
Paolo
Paolo Bonzini (3):
block: make assertion more generic
block: do not check bdrv_file_open
block: remove separate bdrv_file_open callback
block.c | 17 +++++++----------
block/blkdebug.c | 2 +-
block/blkio.c | 2 +-
block/blkverify.c | 2 +-
block/curl.c | 8 ++++----
block/file-posix.c | 8 ++++----
block/file-win32.c | 4 ++--
block/gluster.c | 8 ++++----
block/iscsi.c | 4 ++--
block/nbd.c | 6 +++---
block/nfs.c | 2 +-
block/null.c | 4 ++--
block/nvme.c | 2 +-
block/rbd.c | 3 ++-
block/ssh.c | 2 +-
block/vvfat.c | 2 +-
include/block/block_int-common.h | 3 ---
17 files changed, 37 insertions(+), 42 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-09 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 8:50 Paolo Bonzini [this message]
2023-03-09 8:50 ` [PATCH 1/3] block: make assertion more generic Paolo Bonzini
2023-03-09 8:50 ` [PATCH 2/3] block: do not check bdrv_file_open Paolo Bonzini
2023-03-09 8:50 ` [PATCH 3/3] block: remove separate bdrv_file_open callback Paolo Bonzini
2023-03-09 9:37 ` [PATCH 0/3] " Philippe Mathieu-Daudé
2023-04-05 12:19 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2022-12-12 13:16 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=20230309085051.308664-1-pbonzini@redhat.com \
--to=pbonzini@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).