From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Devin Nakamura <devin122@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] QED block conversion
Date: Tue, 20 Sep 2011 10:58:09 +0100 [thread overview]
Message-ID: <20110920095809.GB16352@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4E7850ED.9030702@redhat.com>
On Tue, Sep 20, 2011 at 10:38:05AM +0200, Kevin Wolf wrote:
> Am 12.09.2011 16:47, schrieb Devin Nakamura:
> > This patch series adds support for block conversion to the qed driver.
> > This depends on my precivious block conversion api series
> > Devin Nakamura (6):
> > qed: add qed_find_cluster_sync()
> > qed: add bdrv_qed_get_conversion_options()
> > qed: add open_conversion_target()
> > qed: add qed_bdrv_get_mapping()
> > qed: add bdrv_qed_map()
> > qed: add bdrv_qed_copy_header()
> >
> > block/qed-cluster.c | 33 +++++++++++
> > block/qed.c | 161 +++++++++++++++++++++++++++++++++++++++++++++++++++
> > block/qed.h | 4 +
> > 3 files changed, 198 insertions(+), 0 deletions(-)
>
> Stefan, can you have a look at this series? I'm reviewing it right now,
> but I'm not that familiar with the details of the QED implementation.
Sure it's in my review queue, will try to get around to it soon.
Stefan
prev parent reply other threads:[~2011-09-20 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 14:47 [Qemu-devel] [PATCH 0/6] QED block conversion Devin Nakamura
2011-09-12 14:47 ` [Qemu-devel] [PATCH 1/6] qed: add qed_find_cluster_sync() Devin Nakamura
2011-09-21 12:45 ` Stefan Hajnoczi
2011-09-21 13:02 ` Kevin Wolf
2011-09-12 14:47 ` [Qemu-devel] [PATCH 2/6] qed: add bdrv_qed_get_conversion_options() Devin Nakamura
2011-09-12 14:47 ` [Qemu-devel] [PATCH 3/6] qed: add open_conversion_target() Devin Nakamura
2011-09-20 9:21 ` Kevin Wolf
2011-09-21 12:37 ` Stefan Hajnoczi
2011-09-20 8:38 ` [Qemu-devel] [PATCH 0/6] QED block conversion Kevin Wolf
2011-09-20 9:58 ` Stefan Hajnoczi [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=20110920095809.GB16352@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=devin122@gmail.com \
--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).