qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Use error_is_set() only when necessary
Date: Fri, 21 Feb 2014 12:01:52 +0100	[thread overview]
Message-ID: <20140221110152.GA3346@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1391090848-2115-1-git-send-email-armbru@redhat.com>

Am 30.01.2014 um 15:07 hat Markus Armbruster geschrieben:
> 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.  Dumb it down to
> obvious.
> 
> Gets rid of several dozen Coverity false positives.
> 
> Note that the obvious form is already used in many places.
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  block.c                            | 16 +++++++--------
>  block/blkdebug.c                   |  4 ++--
>  block/blkverify.c                  |  2 +-
>  block/curl.c                       |  2 +-
>  block/gluster.c                    |  2 +-
>  block/iscsi.c                      |  2 +-
>  block/nbd.c                        |  2 +-
>  block/qapi.c                       |  4 ++--
>  block/qcow2.c                      |  6 +++---
>  block/raw-posix.c                  | 12 +++++------
>  block/raw-win32.c                  |  4 ++--
>  block/raw_bsd.c                    |  2 +-
>  block/rbd.c                        |  2 +-
>  block/sheepdog.c                   |  2 +-
>  block/snapshot.c                   |  2 +-
>  block/vvfat.c                      |  2 +-
>  blockdev.c                         | 42 +++++++++++++++++++-------------------
>  blockjob.c                         |  4 ++--

In the future, can you pleas take readability shit that causes conflicts
left and right through the appropriate subtree so that the burden of
fixing up things isn't on the maintainers?

The above files have _nothing_ to do with QMP.

Had I seen this in time before it was pulled, I would have nacked it for
going through (and therefore being based on) the wrong tree.

Kevin

>  hmp.c                              |  8 ++++----
>  hw/pci/pci-hotplug-old.c           |  4 ++--
>  hw/usb/dev-network.c               |  2 +-
>  net/net.c                          | 12 +++++------
>  qdev-monitor.c                     |  2 +-
>  qemu-char.c                        |  6 +++---
>  qemu-img.c                         |  8 ++++----
>  qga/commands-posix.c               | 18 ++++++++--------
>  qga/commands-win32.c               |  2 +-
>  savevm.c                           |  4 ++--
>  tests/test-qmp-input-strict.c      | 16 +++++++--------
>  tests/test-qmp-input-visitor.c     | 20 +++++++++---------
>  tests/test-qmp-output-visitor.c    | 22 ++++++++++----------
>  tests/test-string-input-visitor.c  | 20 +++++++++---------
>  tests/test-string-output-visitor.c | 14 ++++++-------
>  tpm.c                              |  2 +-
>  util/qemu-config.c                 | 16 +++++++--------
>  util/qemu-option.c                 | 22 ++++++++++----------
>  vl.c                               |  2 +-
>  37 files changed, 156 insertions(+), 156 deletions(-)

      parent reply	other threads:[~2014-02-21 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 14:07 [Qemu-devel] [PATCH] Use error_is_set() only when necessary Markus Armbruster
2014-01-30 15:45 ` Eric Blake
2014-01-30 16:02   ` Markus Armbruster
2014-01-30 17:14 ` Andreas Färber
2014-01-31  7:42   ` Markus Armbruster
2014-02-10 20:54 ` Luiz Capitulino
2014-02-11  1:24   ` Fam Zheng
2014-02-11  8:25     ` Markus Armbruster
2014-02-21 11:01 ` Kevin Wolf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140221110152.GA3346@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).