Laine Stump 55ace7c478 util: report all address range errors in virSocketAddrGetRange() ... There are now many more reasons that virSocketAddrGetRange() could fail, so it is much more informative to report the error there instead of in the caller. (one of the two callers was previously assuming success, which is almost surely safe based on the parsing that has already happened to the config by that time, but it still is nicer to account for an error "just in case") Part of fix for: https://bugzilla.redhat.com/show_bug.cgi?id=985653		2015-06-02 12:40:07 -04:00
..
bridge_driver_linux.c	Fix common misspellings	2015-03-23 09:01:30 +01:00
bridge_driver_nop.c	Replace virNetworkObjPtr with virNetworkDefPtr in network platform APIs	2014-04-25 15:44:09 +01:00
bridge_driver_platform.c	bridge driver: extract platform specifics	2013-08-01 15:47:02 -06:00
bridge_driver_platform.h	struct _virNetworkDriverState: Annotate items	2015-03-13 15:55:56 +01:00
bridge_driver.c	util: report all address range errors in virSocketAddrGetRange()	2015-06-02 12:40:07 -04:00
bridge_driver.h	Fix build --without-network	2015-05-13 15:04:41 +02:00
default.xml	Remove the space before the slash in network XML	2013-08-28 08:05:46 +02:00
leaseshelper.c	leaseshelper: Fix incorrect alignment of a switch case	2014-12-03 18:47:24 +01:00