From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster
Date: Tue, 27 Oct 2020 12:07:53 +0100 [thread overview]
Message-ID: <20201027110753.GB4628@merkur.fritz.box> (raw)
In-Reply-To: <cover.1603731354.git.berto@igalia.com>
Am 26.10.2020 um 17:58 hat Alberto Garcia geschrieben:
> I had to rebase the series due to conflicting changes on master. There
> are no other differences.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2020-10-27 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 16:58 [PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster Alberto Garcia
2020-10-26 16:58 ` [PATCH v5 1/2] qcow2: Report BDRV_BLOCK_ZERO more accurately in bdrv_co_block_status() Alberto Garcia
2020-10-26 16:58 ` [PATCH v5 2/2] qcow2: Skip copy-on-write when allocating a zero cluster Alberto Garcia
2020-10-27 11:07 ` 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=20201027110753.GB4628@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).