All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] simple block driver cleanups
Date: Tue, 4 May 2010 15:22:18 +0200	[thread overview]
Message-ID: <20100504132218.GA12186@lst.de> (raw)
In-Reply-To: <4BE0152F.3060109@redhat.com>

On Tue, May 04, 2010 at 02:38:07PM +0200, Kevin Wolf wrote:
> Am 04.05.2010 12:43, schrieb Christoph Hellwig:
> > This series cleans up the simple read-only block drivers to use the
> > qemu block device API to access their backing devices, making the code
> > simpler and usable over nbd/curl.  I've not touched dmg yet as it's even
> > more bitrot than usual and deserves it's own series.
> 
> Have you already added something to qemu-iotests locally to test this or
> did you test manually?

I tested cloop manually, I haven't found usable creation tools for the
others yet.

  reply	other threads:[~2010-05-04 13:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 10:43 [Qemu-devel] simple block driver cleanups Christoph Hellwig
2010-05-04 10:44 ` [Qemu-devel] [PATCH 2/6] bochs: use qemu block API Christoph Hellwig
2010-05-04 10:44 ` [Qemu-devel] [PATCH 3/6] cloop: use pread Christoph Hellwig
2010-05-04 10:44 ` [Qemu-devel] [PATCH 4/6] cloop: use qemu block API Christoph Hellwig
2010-05-04 10:45 ` [Qemu-devel] [PATCH 5/6] parallels: use pread Christoph Hellwig
2010-05-05 14:19   ` Kevin Wolf
2010-05-05 18:11     ` Christoph Hellwig
2010-05-04 10:45 ` [Qemu-devel] [PATCH 6/6] parallels: use qemu block API Christoph Hellwig
2010-05-04 12:38 ` [Qemu-devel] simple block driver cleanups Kevin Wolf
2010-05-04 13:22   ` Christoph Hellwig [this message]
2010-05-05 14:28     ` Kevin Wolf
2010-05-05 18:10       ` 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=20100504132218.GA12186@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.