Remove pointless virLXCProcessMonitorDestroy method

Asynchronously setting priv->mon to NULL was pointless,
just remove the destroy callback entirely.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
(cherry picked from commit dd0371764f90f31fa8e596b40c0269cdbd5082f6)
This commit is contained in:
Daniel P. Berrange 2012-09-24 15:13:10 +01:00 committed by Cole Robinson
parent df2b4be5cb
commit c9791620a0

View File

@ -554,20 +554,6 @@ cleanup:
}
static void virLXCProcessMonitorDestroy(virLXCMonitorPtr mon,
virDomainObjPtr vm)
{
virLXCDomainObjPrivatePtr priv;
virDomainObjLock(vm);
priv = vm->privateData;
if (priv->monitor == mon)
priv->monitor = NULL;
if (virObjectUnref(vm))
virDomainObjUnlock(vm);
}
extern virLXCDriverPtr lxc_driver;
static void virLXCProcessMonitorEOFNotify(virLXCMonitorPtr mon ATTRIBUTE_UNUSED,
virDomainObjPtr vm)
@ -649,7 +635,6 @@ static void virLXCProcessMonitorExitNotify(virLXCMonitorPtr mon ATTRIBUTE_UNUSED
static virLXCMonitorCallbacks monitorCallbacks = {
.eofNotify = virLXCProcessMonitorEOFNotify,
.destroy = virLXCProcessMonitorDestroy,
.exitNotify = virLXCProcessMonitorExitNotify,
};