From: Kevin Wolf <kwolf@redhat.com>
To: bharata@linux.vnet.ibm.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Anand Avati <aavati@redhat.com>,
Vijay Bellur <vbellur@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Harsh Bora <harsh@linux.vnet.ibm.com>,
Amar Tumballi <amarts@redhat.com>,
qemu-devel@nongnu.org, Daniel Veillard <veillard@redhat.com>,
Blue Swirl <blauwirbel@gmail.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
Avi Kivity <avi@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v10 0/5] GlusterFS support in QEMU - v10
Date: Fri, 28 Sep 2012 20:23:59 +0200 [thread overview]
Message-ID: <5065EB3F.4030806@redhat.com> (raw)
In-Reply-To: <20120927135553.GD18285@in.ibm.com>
Am 27.09.2012 15:55, schrieb Bharata B Rao:
> Hi,
>
> This is v10 of the patchset to support GlusterFS backend from QEMU.
>
> Changes in v10
> --------------
> - Included another fix to qemu_aio_wait() from Paolo in the series.
> - A few more fixes to the volume and image parsing code.
> - Removed unnecessary unescaping of URI query parameters.
> - Fail if server or port are specified for unix type of transport.
> - Save errno in case glfs_fini() fails in qemu_gluster_init().
> - s/qemu_gluster_send_pipe/qemu_write_full
> - Remove unnecessary clearing of O_ACCMODE from open_flags in qemu_gluster_open.
>
> Previous versions can be found here:
>
> v9 - http://lists.nongnu.org/archive/html/qemu-devel/2012-09/msg04016.html
> v8 - http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg04007.html
> v7 - http://lists.nongnu.org/archive/html/qemu-devel/2012-09/msg02532.html
> v6 - http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg01536.html
> v5 - http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg01023.html
> v4 - http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg00147.html
> v3 - http://lists.nongnu.org/archive/html/qemu-devel/2012-07/msg03322.html
> v2 - http://lists.nongnu.org/archive/html/qemu-devel/2012-07/msg02718.html
> v1 - http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg01745.html
Thanks, applied all to the block branch.
Kevin
prev parent reply other threads:[~2012-09-28 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 13:55 [Qemu-devel] [PATCH v10 0/5] GlusterFS support in QEMU - v10 Bharata B Rao
2012-09-27 13:56 ` [Qemu-devel] [PATCH v10 1/5] aio: Fix qemu_aio_wait() to maintain correct walking_handlers count Bharata B Rao
2012-09-27 13:57 ` [Qemu-devel] [PATCH v10 2/5] aio: Another fix to the walking_handlers logic Bharata B Rao
2012-09-27 13:58 ` [Qemu-devel] [PATCH v10 3/5] qemu: URI parsing library Bharata B Rao
2012-09-27 14:36 ` Daniel P. Berrange
2012-09-27 15:55 ` Paolo Bonzini
2012-09-28 8:39 ` Daniel P. Berrange
2012-09-28 9:47 ` Paolo Bonzini
2012-09-27 13:59 ` [Qemu-devel] [PATCH v10 4/5] configure: Add a config option for GlusterFS as block backend Bharata B Rao
2012-09-27 14:00 ` [Qemu-devel] [PATCH v10 5/5] block: Support GlusterFS as a QEMU " Bharata B Rao
2012-09-28 18:23 ` Kevin Wolf [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=5065EB3F.4030806@redhat.com \
--to=kwolf@redhat.com \
--cc=aavati@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amarts@redhat.com \
--cc=avi@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=harsh@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@gmail.com \
--cc=vbellur@redhat.com \
--cc=veillard@redhat.com \
/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.