Use error_is_set() only when necessary (again)
authorMarkus Armbruster <armbru@redhat.com>
Fri, 25 Apr 2014 14:50:31 +0000 (16:50 +0200)
committerStefan Hajnoczi <stefanha@redhat.com>
Fri, 25 Apr 2014 16:05:06 +0000 (18:05 +0200)
commit0fb6395c0cb5046432a80d608ddde7a3b2f8a9ae
treebc4d5b75394733d277652b127066461b7197c360
parenta28315ebaf3910b65ef51abefc4ef040265afc19
Use error_is_set() only when necessary (again)

error_is_set(&var) is the same as var != NULL, but it takes
whole-program analysis to figure that out.  Unnecessarily hard for
optimizers, static checkers, and human readers.  Commit 84d18f0 dumbed
it down to obvious, but a few more have crept in since, and
documentation was overlooked.  Dumb these down, too.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
block.c
block/mirror.c
block/nfs.c
block/quorum.c
docs/writing-qmp-commands.txt
tests/test-qmp-input-strict.c