There are two places where a variable passed to VBOX_RELEASE()
macro is set to NULL explicitly. There is no need for that
because the macro sets the variable to NULL already.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
src/vbox/vbox_common.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/vbox/vbox_common.c b/src/vbox/vbox_common.c
index eec47a02fc..db54eacb3b 100644
--- a/src/vbox/vbox_common.c
+++ b/src/vbox/vbox_common.c
@@ -2808,7 +2808,6 @@ static int vboxDomainGetInfo(virDomainPtr dom, virDomainInfoPtr
info)
if (systemProperties) {
gVBoxAPI.UISystemProperties.GetMaxGuestRAM(systemProperties,
&maxMemorySize);
VBOX_RELEASE(systemProperties);
- systemProperties = NULL;
}
gVBoxAPI.UIMachine.GetCPUCount(machine, &CPUCount);
@@ -4015,7 +4014,6 @@ static char *vboxDomainGetXMLDesc(virDomainPtr dom, unsigned int
flags)
gVBoxAPI.UISystemProperties.GetSerialPortCount(systemProperties,
&serialPortCount);
gVBoxAPI.UISystemProperties.GetParallelPortCount(systemProperties,
¶llelPortCount);
VBOX_RELEASE(systemProperties);
- systemProperties = NULL;
}
/* Currently setting memory and maxMemory as same, cause
* the notation here seems to be inconsistent while
--
2.34.1