Markus Armbruster 65cd9064e1 qom: Clean up fragile use of error_is_set() in set() methods ... Using error_is_set(ERRP) to find out whether a function failed is either wrong, fragile, or unnecessarily opaque. It's wrong when ERRP may be null, because errors go undetected when it is. It's fragile when proving ERRP non-null involves a non-local argument. Else, it's unnecessarily opaque (see commit 84d18f0). I guess the error_is_set(errp) in the ObjectProperty set() methods are merely fragile right now, because I can't find a call chain that passes a null errp argument. Make the code more robust and more obviously correct: receive the error in a local variable, then propagate it through the parameter. Signed-off-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Andreas Färber <afaerber@suse.de>		2014-05-05 19:08:49 +02:00
..
dataplane	dataplane: fix shadowed return value	2014-01-22 13:48:18 +01:00
Makefile.objs	virtio: Implement MMIO based virtio transport	2013-07-19 12:58:47 +01:00
vhost.c	vhost: clear signalled_used_valid on vhost stop	2013-08-12 12:25:17 +03:00
virtio-balloon.c	qom: Clean up fragile use of error_is_set() in set() methods	2014-05-05 19:08:49 +02:00
virtio-bus.c	virtio-bus: cleanup plug/unplug interface	2013-12-09 21:46:48 +01:00
virtio-mmio.c	virtio-bus: remove vdev field	2013-12-09 21:46:48 +01:00
virtio-pci.c	qom: Add check() argument to object_property_add_link()	2014-03-19 22:23:13 +01:00
virtio-pci.h	virtio-pci: remove vdev field	2013-12-09 21:46:48 +01:00
virtio-rng.c	virtio-rng: Avoid default_backend refcount leak	2014-03-19 22:23:47 +01:00
virtio.c	exec: Make stw_*_phys input an AddressSpace	2014-02-11 22:57:32 +10:00