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
bridge_driver_nop.c
bridge_driver_platform.c
bridge_driver_platform.h
bridge_driver.c	util: report all address range errors in virSocketAddrGetRange()	2015-06-02 12:40:07 -04:00
bridge_driver.h
default.xml
leaseshelper.c