Re: [Xen-devel] [PATCH] qemu-trad: xenstore: use relative path for device-model node

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Wei Liu writes ("Re: [PATCH] qemu-trad: xenstore: use relative path for 
device-model node"):
> On Thu, Apr 09, 2015 at 06:46:31PM +0100, Ian Jackson wrote:
> > Right.  So that means that this patch needs to go in at the same time
> > as the corresponding libxl change.
> 
> I don't follow "go in at the same time". They are in two different
> trees, don't they?

The commit id of the qemu-trad tree is in Config.mk in xen.git.  So it
is possible to update them "simultaneously".  (Of course not every way
of building and deploying Xen will honour this, but if you don't
honour it you deserve what you get.)

> > And the answer is that unless both libxl and qemu change at the same
> > time, it would be a regression in -unstable ?
> 
> It would be a regression because stubdom in -unstable is working now
> with Paul's workaround. So yes, both changes need to go in at the same
> time -- though I don't know how you would do that.

Right.  That's what the Config.mk update is for.

So if the libxl patch is otherwise ready, we can commit both at once.
I will commit and push to qemu-trad, update the libxl patch to contain
the Config.mk update as well, and push the result to xen.git.

We normally explain the need to do this in the commit message for the
patches, and cross reference the two commits.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel