From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] cow: use qemu block API
Date: Tue, 08 Jun 2010 18:50:29 +0200 [thread overview]
Message-ID: <4C0E74D5.1090209@redhat.com> (raw)
In-Reply-To: <20100607100647.GC2176@lst.de>
Am 07.06.2010 12:06, schrieb Christoph Hellwig:
> Use bdrv_pwrite to access the backing device instead of pread, and
> convert the driver to implementing the bdrv_open method which gives
> it an already opened BlockDriverState for the underlying device.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Thanks, applied all to the block branch.
Kevin
next prev parent reply other threads:[~2010-06-08 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 10:06 [Qemu-devel] [PATCH 3/3] cow: use qemu block API Christoph Hellwig
2010-06-07 12:27 ` Markus Armbruster
2010-06-08 8:52 ` Christoph Hellwig
2010-06-08 16:50 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-07 15:16 [Qemu-devel] [PATCH 0/3] cow conversion to the " Christoph Hellwig
2010-05-07 15:17 ` [Qemu-devel] [PATCH 3/3] cow: use qemu " Christoph Hellwig
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=4C0E74D5.1090209@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@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).