On Thu, Aug 02, 2012 at 11:13:20AM +0100, Daniel P. Berrange wrote:
> On Wed, Aug 01, 2012 at 04:39:24PM +0800, Hu Tao wrote:
> > > void
> > > virBlkioDeviceWeightArrayClear(virBlkioDeviceWeightPtr deviceWeights,
> > > int ndevices)
> > > @@ -723,7 +738,7 @@ virDom
On Wed, Aug 01, 2012 at 04:39:24PM +0800, Hu Tao wrote:
> > void
> > virBlkioDeviceWeightArrayClear(virBlkioDeviceWeightPtr deviceWeights,
> > int ndevices)
> > @@ -723,7 +738,7 @@ virDomainObjListDataFree(void *payload, const void
> > *name ATTRIBUTE_UNUSED)
> >
> void
> virBlkioDeviceWeightArrayClear(virBlkioDeviceWeightPtr deviceWeights,
> int ndevices)
> @@ -723,7 +738,7 @@ virDomainObjListDataFree(void *payload, const void *name
> ATTRIBUTE_UNUSED)
> {
> virDomainObjPtr obj = payload;
> virDomainObjLock(obj
From: "Daniel P. Berrange"
Switch virDomainObjPtr to use the virObject APIs for reference
counting. The main change is that virObjectUnref does not return
the reference count, merely a bool indicating whether the object
still has any refs left. Checking the return value is also not
mandatory.
Si
On 07/11/2012 07:35 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Switch virDomainObjPtr to use the virObject APIs for reference
> counting. The main change is that virObjectUnref does not return
> the reference count, merely a bool indicating whether the object
> still has any r
From: "Daniel P. Berrange"
Switch virDomainObjPtr to use the virObject APIs for reference
counting. The main change is that virObjectUnref does not return
the reference count, merely a bool indicating whether the object
still has any refs left. Checking the return value is also not
mandatory.
Si
