From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/2] reject qcow2 creation with protocol in data_store
Date: Tue, 4 Nov 2025 18:26:20 +0100 [thread overview]
Message-ID: <aQo3PB3wEJqSKTdP@redhat.com> (raw)
In-Reply-To: <20250915213919.3121401-4-eblake@redhat.com>
Am 15.09.2025 um 23:37 hat Eric Blake geschrieben:
> v2 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2025-05/msg06231.html
> Since then:
> - rebase to latest tree
>
> Eric Blake (2):
> block: Allow drivers to control protocol prefix at creation
> qcow2, vmdk: Restrict creation with secondary file using protocol
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2025-11-04 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 21:37 [PATCH v3 0/2] reject qcow2 creation with protocol in data_store Eric Blake
2025-09-15 21:37 ` [PATCH v3 1/2] block: Allow drivers to control protocol prefix at creation Eric Blake
2025-09-15 21:37 ` [PATCH v3 2/2] qcow2, vmdk: Restrict creation with secondary file using protocol Eric Blake
2025-10-15 18:30 ` [PATCH v3 0/2] reject qcow2 creation with protocol in data_store Eric Blake
2025-11-04 17:26 ` Kevin Wolf [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=aQo3PB3wEJqSKTdP@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--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).