Since .io_flush() is no longer called we do not need
qemu_gluster_aio_flush_cb() anymore. It turns out that qemu_aio_count
is unused now and can be dropped.
Thanks to Bharata B Rao for catching a
build failure with CONFIG_GLUSTERFS_DISCARD, which has been fixed.
Signed-off-by: Stefan Hajnoczi
On Sat, Aug 17, 2013 at 10:52:34AM +0530, Bharata B Rao wrote:
> > From: Stefan Hajnoczi
> > Since .io_flush() is no longer called we do not need
> > qemu_gluster_aio_flush_cb() anymore. It turns out that qemu_aio_count
> > is unused now and can be dropped.
> >
> > Signed-off-by: Stefan Hajnoczi
> From: Stefan Hajnoczi
> Since .io_flush() is no longer called we do not need
> qemu_gluster_aio_flush_cb() anymore. It turns out that qemu_aio_count
> is unused now and can be dropped.
>
> Signed-off-by: Stefan Hajnoczi
Tested-by: Bharata B Rao
Tested GlusterFS backend, but it needed the b
Since .io_flush() is no longer called we do not need
qemu_gluster_aio_flush_cb() anymore. It turns out that qemu_aio_count
is unused now and can be dropped.
Signed-off-by: Stefan Hajnoczi
---
block/gluster.c | 16 +---
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/bl
