Markus Armbruster 0aff637e92 char: Clean up fragile use of error_is_set()
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).

The error_is_set(errp) in qemu_chr_new_from_opts() is merely fragile,
because the callers never pass 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: Gerd Hoffmann <kraxel@redhat.com>
2014-05-21 11:57:58 +02:00
2014-04-23 10:28:14 +02:00
2014-05-16 10:35:59 -04:00
2014-04-25 12:59:57 +02:00
2014-05-15 14:24:05 +02:00
2014-05-09 09:11:31 -04:00
2014-05-15 14:24:05 +02:00
2014-05-16 10:35:59 -04:00
2014-04-25 09:19:58 -04:00
2014-05-15 16:24:12 +01:00
2014-05-16 10:35:59 -04:00
2014-05-16 08:30:12 +02:00
2014-04-28 08:55:31 +04:00
2014-05-14 15:24:51 +02:00
2013-10-11 09:34:56 -07:00
2014-05-15 18:56:08 +01:00
2014-03-13 14:34:16 +00:00
2014-04-18 10:33:36 +04:00
2014-04-22 12:00:20 +02:00
2014-04-22 12:00:20 +02:00
2014-04-28 13:43:17 +01:00
2014-05-09 22:59:40 +02:00
2014-05-19 12:53:07 +01:00
2014-04-17 20:39:32 +01:00
2014-05-09 20:57:32 +02:00
2014-05-07 16:16:43 +00:00

Read the documentation in qemu-doc.html or on http://wiki.qemu-project.org

- QEMU team
Description
No description provided
Readme 404 MiB
Languages
C 82.6%
C++ 6.5%
Python 3.4%
Dylan 2.9%
Shell 1.6%
Other 2.8%