From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: libvir-list <libvir-list@redhat.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xensource.com
Subject: Re: [libvirt] [PATCH] libxl: don't break the build on Xen>=4.5 because of libxl_vcpu_setaffinity()
Date: Tue, 1 Jul 2014 11:03:47 +0200 [thread overview]
Message-ID: <1404205427.8515.191.camel@Solace> (raw)
In-Reply-To: <1404201685.1829.115.camel@dagon.hellion.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1718 bytes --]
On mar, 2014-07-01 at 09:01 +0100, Ian Campbell wrote:
> On Tue, 2014-07-01 at 08:52 +0200, Dario Faggioli wrote:
> > On lun, 2014-06-30 at 15:32 -0600, Jim Fehlig wrote:
> > > Eric Blake wrote:
> > >
> > > >> Thanks, looks good. I was about to push, but wanted to check with other
> > > >> libvirt devs first since we are in 1.2.6 freeze. Would it be fine to
> > > >> push this? It fixes a libxl driver build failure against xen-unstable.
> > > >>
> > > >
> > > > Yes, fixing a build failure is an acceptable fix during hard freeze. Go
> > > > ahead and push.
> > > >
> > >
> > > Thanks Eric, pushed now.
> > >
> > Cool! Thanks Everyone,
>
> And thanks Dario for the quick fix.
>
Well, it could (and should!) have been quicker, but it collapsed with an
update of the test box I devote to Xen+libvirt hack/testing...
I've added "keep that box in a more good shape" to my menta
checklist. :-)
> I've added "does libvirt need a peemptive update?" to my mental
> checklist for things involved LIBXL_API_VERSION changes.
>
Me too, and actually, looking at things from this perspective, I think
the push gate did a good job _as_it_is_ in highlighting how much careful
we should be with the libxl interface, and that things either get fixed
quickly or changes be reverted.
Just thinking out loud here but, if we did not get the push failure,
when would have we discovered this?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-07-01 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 17:19 [libvirt] [PATCH] libxl: don't break the build on Xen>=4.5 because of libxl_vcpu_setaffinity() Dario Faggioli
2014-06-30 21:11 ` Jim Fehlig
2014-06-30 21:23 ` [libvirt] " Eric Blake
2014-06-30 21:32 ` Jim Fehlig
2014-07-01 6:52 ` Dario Faggioli
2014-07-01 8:01 ` Ian Campbell
2014-07-01 9:03 ` Dario Faggioli [this message]
2014-07-01 17:00 ` Jim Fehlig
2014-07-02 9:14 ` Ian Campbell
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=1404205427.8515.191.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xensource.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.