From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, famz@redhat.com,
jcody@redhat.com, pbonzini@redhat.com, pavel.dovgaluk@ispras.ru,
mreitz@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH 0/2] block: make .bdrv_close optional
Date: Tue, 14 Aug 2018 15:17:14 +0200 [thread overview]
Message-ID: <20180814131714.GM5025@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <20180814124320.39481-1-vsementsov@virtuozzo.com>
Am 14.08.2018 um 14:43 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Several block drivers have to define empty .bdrv_close handler. Let's
> instead make it optional.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2018-08-14 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:43 [Qemu-devel] [PATCH 0/2] block: make .bdrv_close optional Vladimir Sementsov-Ogievskiy
2018-08-14 12:43 ` [Qemu-devel] [PATCH 1/2] " Vladimir Sementsov-Ogievskiy
2018-08-14 12:43 ` [Qemu-devel] [PATCH 2/2] block: drop empty .bdrv_close handlers Vladimir Sementsov-Ogievskiy
2018-08-14 13:17 ` 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=20180814131714.GM5025@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=mreitz@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@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).