From: Wei Liu <wei.liu2@citrix.com>
To: Jim Fehlig <jfehlig@suse.com>
Cc: libvir-list@redhat.com,
Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Fixing libvirt's libxl driver breakage -- where to define LIBXL_API_VERSION?
Date: Tue, 12 Apr 2016 23:06:24 +0100 [thread overview]
Message-ID: <20160412220624.GA20356__33398.0010626421$1460498895$gmane$org@citrix.com> (raw)
In-Reply-To: <570D6942.8020106@suse.com>
On Tue, Apr 12, 2016 at 03:31:46PM -0600, Jim Fehlig wrote:
> Wei Liu wrote:
> > Hi libvirt maintainers,
>
> Sorry for the delay. Slowly catching up on mail after vacation...
>
> >
> > Xen's control library libxenlight (libxl) requires application
> > (libvirt in this case) to explictily define LIBXL_API_VERSION.
>
> Where is this requirement written? :-)
>
> > This is
> > lacking at the moment so libvirt's libxl driver always gets the latest
> > APIs.
>
> IMO, that is what we want for upstream libvirt. Downstreams can choose a
> specific version if they want.
>
> > We changed one of the APIs in libxl so libvirt's libxl driver
> > can't build at the moment.
>
> A quick glance ahead in my libvirt mail tells me you fixed this with the
> preferred LIBXL_HAVE_* pattern.
>
It's already done that way. :-)
Wei.
> Regards,
> Jim
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-12 22:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160405113936.GA18120@citrix.com>
2016-04-12 21:31 ` Fixing libvirt's libxl driver breakage -- where to define LIBXL_API_VERSION? Jim Fehlig
[not found] ` <570D6942.8020106@suse.com>
2016-04-12 22:06 ` Wei Liu [this message]
2016-04-13 9:09 ` George Dunlap
2016-04-13 9:26 ` [libvirt] " Daniel P. Berrange
[not found] ` <20160413092654.GE8847@redhat.com>
2016-04-13 9:50 ` George Dunlap
2016-04-13 13:28 ` Wei Liu
2016-04-13 23:44 ` Jim Fehlig
[not found] ` <570ED9DF.5070606@suse.com>
2016-06-27 15:33 ` Ian Jackson
2016-06-27 15:54 ` Ian Jackson
2016-06-27 16:03 ` Daniel P. Berrange
2016-06-27 16:12 ` Ian Jackson
2016-06-27 16:17 ` Daniel P. Berrange
2016-06-27 16:35 ` Jim Fehlig
2016-06-27 16:54 ` Ian Jackson
2016-06-28 7:01 ` Jan Beulich
2016-06-28 10:42 ` Ian Jackson
2016-04-13 23:31 ` Jim Fehlig
[not found] ` <570ED6B4.3060102@suse.com>
2016-04-14 7:40 ` Dario Faggioli
[not found] ` <1460619652.13871.130.camel@citrix.com>
2016-04-14 17:59 ` Ian Jackson
2016-04-14 18:05 ` Dario Faggioli
2016-04-15 9:14 ` Olaf Hering
2016-04-05 11:39 Wei Liu
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='20160412220624.GA20356__33398.0010626421$1460498895$gmane$org@citrix.com' \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jfehlig@suse.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xenproject.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).