From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Stefan Weil <sw@weilnetz.de>, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] vdi: Implement .bdrv_co_create
Date: Tue, 13 Mar 2018 11:22:40 +0100 [thread overview]
Message-ID: <20180313102240.GA4642@localhost.localdomain> (raw)
In-Reply-To: <20180312165528.8969-1-mreitz@redhat.com>
Am 12.03.2018 um 17:55 hat Max Reitz geschrieben:
> I think cluster-size should not be exposed in QAPI (yet), but Kevin's
> patch does that, while I had these patches lying around, so here is my
> proposal.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2018-03-13 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 16:55 [Qemu-devel] [PATCH 0/3] vdi: Implement .bdrv_co_create Max Reitz
2018-03-12 16:55 ` [Qemu-devel] [PATCH 1/3] vdi: Pull option parsing from vdi_co_create Max Reitz
2018-03-12 16:55 ` [Qemu-devel] [PATCH 2/3] vdi: Move file creation to vdi_co_create_opts Max Reitz
2018-03-12 16:55 ` [Qemu-devel] [PATCH 3/3] vdi: Implement .bdrv_co_create Max Reitz
2018-03-13 10:22 ` 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=20180313102240.GA4642@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).