From: Kevin Wolf <kwolf@redhat.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, den@virtuozzo.com, qemu-block@nongnu.org,
qemu-stable@nongnu.org, mreitz@redhat.com, pl@kamp.de
Subject: Re: [Qemu-devel] [PATCH v3 1/1] qemu-img: wait for convert coroutines to complete
Date: Tue, 9 May 2017 17:25:23 +0200 [thread overview]
Message-ID: <20170509152523.GI5243@noname.str.redhat.com> (raw)
In-Reply-To: <1493195595-4809-1-git-send-email-anton.nefedov@virtuozzo.com>
Am 26.04.2017 um 10:33 hat Anton Nefedov geschrieben:
> On error path (like i/o error in one of the coroutines), it's required to
> - wait for coroutines completion before cleaning the common structures
> - reenter dependent coroutines so they ever finish
>
> Introduced in 2d9187bc65.
>
> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2017-05-09 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 8:33 [Qemu-devel] [PATCH v3 1/1] qemu-img: wait for convert coroutines to complete Anton Nefedov
2017-04-27 19:09 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2017-05-09 15:25 ` 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=20170509152523.GI5243@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).