qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, armbru@redhat.com
Subject: [Qemu-devel] [PATCH 0/8] block: bdrv_img_create(): propagate errors
Date: Wed, 17 Oct 2012 16:35:48 -0300	[thread overview]
Message-ID: <1350502556-4885-1-git-send-email-lcapitulino@redhat.com> (raw)

This series is a first step to propagate errors from bdrv_open(), but it also
improves qmp_transaction() error messages on bdrv_img_create() failures plus
some other improvements.

Please, check individual patches for details.

o From the RFC

 - Better testing
 - improved changelogs
 - small simplifications

Luiz Capitulino (7):
  block: bdrv_img_create(): add param_list argument
  block: bdrv_img_create(): move parameter list printing to qemu-img
  block: bdrv_img_create(): add Error ** argument
  qemu-img: img_create(): use Error object
  qemu-img: img_create(): simplify
  qmp: qmp_transaction(): pass Error object to bdrv_img_create()
  block: bdrv_img_create(): drop unused error handling code

Paolo Bonzini (1):
  error: add error_set_errno and error_setg_errno

 block.c    | 69 +++++++++++++++++++++++++++-----------------------------------
 block.h    |  7 ++++---
 blockdev.c | 13 ++++++------
 error.c    | 28 +++++++++++++++++++++++++
 error.h    |  9 ++++++++
 qemu-img.c | 26 +++++++++++++++--------
 6 files changed, 95 insertions(+), 57 deletions(-)

-- 
1.7.12.315.g682ce8b

             reply	other threads:[~2012-10-17 19:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 19:35 Luiz Capitulino [this message]
2012-10-17 19:35 ` [Qemu-devel] [PATCH 1/8] error: add error_set_errno and error_setg_errno Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 2/8] block: bdrv_img_create(): add param_list argument Luiz Capitulino
2012-10-18 11:57   ` Kevin Wolf
2012-10-18 13:33     ` Luiz Capitulino
2012-10-18 17:18       ` Luiz Capitulino
2012-10-19  9:13         ` Kevin Wolf
2012-10-19 12:49           ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 3/8] block: bdrv_img_create(): move parameter list printing to qemu-img Luiz Capitulino
2012-10-18 12:01   ` Kevin Wolf
2012-10-18 12:16     ` Kevin Wolf
2012-10-18 13:34       ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 4/8] block: bdrv_img_create(): add Error ** argument Luiz Capitulino
2012-10-18 12:08   ` Kevin Wolf
2012-10-18 13:41     ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 5/8] qemu-img: img_create(): use Error object Luiz Capitulino
2012-10-18 12:11   ` Kevin Wolf
2012-10-18 13:49     ` Luiz Capitulino
2012-10-18 14:02       ` Kevin Wolf
2012-10-23  9:58         ` Markus Armbruster
2012-10-23 10:08           ` Kevin Wolf
2012-10-23 13:07             ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 6/8] qemu-img: img_create(): simplify Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 7/8] qmp: qmp_transaction(): pass Error object to bdrv_img_create() Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 8/8] block: bdrv_img_create(): drop unused error handling code Luiz Capitulino

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=1350502556-4885-1-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@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).