From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: Drop synchronous qcow_write()
Date: Wed, 13 May 2009 12:59:17 +0200 [thread overview]
Message-ID: <20090513105917.GA5349@lst.de> (raw)
In-Reply-To: <1242211593-16495-1-git-send-email-kwolf@redhat.com>
On Wed, May 13, 2009 at 12:46:33PM +0200, Kevin Wolf wrote:
> There is only one (internal) user left and it can be switched to the normal
> emulation provided in block.c. Leaving it as it is would mean that creating
> compressed images uses a different codepath than everything else, so there
> would be a risk of a breakage that wouldn't be covered by much testing.
Looks good to me, that strary qcow2_write irked me, too. Do you plan
to kill qcow_read, too?
Also the same patch should into qcow, too.
next prev parent reply other threads:[~2009-05-13 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 10:46 [Qemu-devel] [PATCH] qcow2: Drop synchronous qcow_write() Kevin Wolf
2009-05-13 10:59 ` Christoph Hellwig [this message]
2009-05-13 11:08 ` Kevin Wolf
2009-05-18 11:59 ` 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=20090513105917.GA5349@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--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).