qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com
Subject: [Qemu-devel] [PATCH trivial 0/5] Fix error_report() calls
Date: Wed, 22 Jun 2011 14:03:52 +0200	[thread overview]
Message-ID: <1308744237-3468-1-git-send-email-armbru@redhat.com> (raw)

I limited myself to truly trivial fixes.  I hope that's still useful
enough to excuse a little rant.

"bug: 0 0" is not a useful error message.  Neither are "Desc next is
128", " too short" (too short indeed), "wrong magic" (some "wrong
magic" skills will be handy to figure out what went wrong).  I'm
stopping here for brevity's sake, not for want of examples.

If you can't be bothered to provide an intelligible error message and
*test* it to verify it actually makes sense for the user, maybe you
should stick to assert() or something.  Makes your laziness stand out
properly.

Markus Armbruster (5):
  sheepdog: qemu_bh_new() can't return null pointer, drop check
  Strip trailing '\n' from error_report()'s first argument
  qemu-img: Don't prepend qemu-img to error messages twice.
  Spell "unkown" correctly in error_report() arguments
  blockdev: Put space after comma in error message

 block-migration.c       |    2 +-
 block/qcow2.c           |    2 +-
 block/sheepdog.c        |   90 ++++++++++++++++++++++-------------------------
 blockdev.c              |    2 +-
 hw/lm32_sys.c           |    2 +-
 hw/lm32_timer.c         |    4 +-
 hw/lm32_uart.c          |    4 +-
 hw/milkymist-ac97.c     |    4 +-
 hw/milkymist-memcard.c  |    4 +-
 hw/milkymist-minimac2.c |    6 ++--
 hw/milkymist-pfpu.c     |    4 +-
 hw/milkymist-softusb.c  |    8 ++--
 hw/milkymist-sysctl.c   |    4 +-
 hw/milkymist-tmu2.c     |    8 ++--
 hw/qdev.c               |    2 +-
 hw/strongarm.c          |    4 +-
 hw/usb-ccid.c           |    2 +-
 hw/virtio-serial-bus.c  |   10 +++---
 hw/virtio.c             |    4 +-
 net.c                   |    2 +-
 net/socket.c            |    6 ++--
 qemu-error.c            |    2 +
 qemu-img.c              |   12 +++---
 23 files changed, 92 insertions(+), 96 deletions(-)

-- 
1.7.2.3

             reply	other threads:[~2011-06-22 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 12:03 Markus Armbruster [this message]
2011-06-22 12:03 ` [Qemu-devel] [PATCH trivial 1/5] sheepdog: qemu_bh_new() can't return null pointer, drop check Markus Armbruster
2011-06-22 12:03 ` [Qemu-devel] [PATCH trivial 2/5] Strip trailing '\n' from error_report()'s first argument Markus Armbruster
2011-06-22 12:03 ` [Qemu-devel] [PATCH trivial 3/5] qemu-img: Don't prepend qemu-img to error messages twice Markus Armbruster
2011-06-22 12:03 ` [Qemu-devel] [PATCH trivial 4/5] Spell "unkown" correctly in error_report() arguments Markus Armbruster
2011-06-22 12:03 ` [Qemu-devel] [PATCH trivial 5/5] blockdev: Put space after comma in error message Markus Armbruster
2011-06-22 12:41 ` [Qemu-devel] [PATCH trivial 0/5] Fix error_report() calls Anthony Liguori
2011-06-23 13:33 ` Stefan Hajnoczi

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=1308744237-3468-1-git-send-email-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).