15 Jul
2014
15 Jul
'14
10:05 p.m.
On 07/15/2014 06:38 AM, Michal Privoznik wrote:
There are just two places where we rely on the fact that VIR_FREE() macro is without any side effects. In the future, this property of the macro is going to change, so we need the code to be adjusted to deal with argument passed to VIR_FREE() being evaluated multiple times.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- src/conf/network_conf.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
NACK; my v2 keeps the property, so we don't need to work around it changing after all. https://www.redhat.com/archives/libvir-list/2014-July/msg00760.html -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org