From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Anand Avati <aavati@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Vijay Bellur <vbellur@redhat.com>,
Amar Tumballi <amarts@redhat.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/2] qemu: Add a config option for GlusterFS as block backend
Date: Thu, 9 Aug 2012 13:49:51 +0530 [thread overview]
Message-ID: <20120809081951.GA18244@in.ibm.com> (raw)
In-Reply-To: <50229180.8060705@redhat.com>
On Wed, Aug 08, 2012 at 09:19:12AM -0700, Anand Avati wrote:
>
> It would be best if the autoconf changes is based on pkgconfig as
> shown in https://github.com/gluster/glusterfs/blob/master/api/examples/configure.ac.
> If you do not want to introduce pkgconfig dependency (if you already
> do not have it) then it would be good to adopt the steps mentioned
> in section "2." of
> https://github.com/gluster/glusterfs/blob/master/api/examples/README.
> That would basically mean including "-I/path/include/glusterfs" in
> CPPFLAGS and only "#include <api/glfs.h>" instead of
> <glusterfs/api/glfs.h>.
I don't see others in QEMU doing this currently. I suggest that we
have the current patchset in 1.2 and see if such improvements can be
done subsequently.
Regards,
Bharata.
next prev parent reply other threads:[~2012-08-09 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 7:59 [Qemu-devel] [PATCH v5 0/2] GlusterFS support in QEMU - v5 Bharata B Rao
2012-08-07 8:00 ` [Qemu-devel] [PATCH v5 1/2] qemu: Add a config option for GlusterFS as block backend Bharata B Rao
2012-08-07 20:15 ` Blue Swirl
2012-08-08 8:52 ` Bharata B Rao
2012-08-08 16:19 ` Anand Avati
2012-08-09 8:19 ` Bharata B Rao [this message]
2012-08-07 8:01 ` [Qemu-devel] [PATCH v5 2/2] block: Support GlusterFS as a QEMU " Bharata B Rao
2012-08-08 14:37 ` Stefan Hajnoczi
2012-08-08 15:08 ` Bharata B Rao
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=20120809081951.GA18244@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=aavati@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amarts@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=vbellur@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 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).