From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] block: Two copy offloading corrections
Date: Wed, 27 Jun 2018 14:52:00 +0200 [thread overview]
Message-ID: <20180627125200.GD4340@localhost.localdomain> (raw)
In-Reply-To: <20180627035752.1425-1-famz@redhat.com>
Am 27.06.2018 um 05:57 hat Fam Zheng geschrieben:
> Fam Zheng (2):
> qcow2: Remove dead check on !ret
> block: Move request tracking to children in copy offloading
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2018-06-27 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 3:57 [Qemu-devel] [PATCH 0/2] block: Two copy offloading corrections Fam Zheng
2018-06-27 3:57 ` [Qemu-devel] [PATCH 1/2] qcow2: Remove dead check on !ret Fam Zheng
2018-06-27 13:05 ` Philippe Mathieu-Daudé
2018-06-27 3:57 ` [Qemu-devel] [PATCH 2/2] block: Move request tracking to children in copy offloading Fam Zheng
2018-06-27 10:27 ` [Qemu-devel] [PATCH 0/2] block: Two copy offloading corrections Stefan Hajnoczi
2018-06-27 12:52 ` 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=20180627125200.GD4340@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).