From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Remove NULL checks for bdrv_new return value
Date: Thu, 16 Dec 2010 17:48:31 +0000 [thread overview]
Message-ID: <AANLkTimPYU1XSLDX_RGEbMReWORONa7YWn3r1ST4wGjo@mail.gmail.com> (raw)
In-Reply-To: <1292510661-16106-1-git-send-email-kwolf@redhat.com>
On Thu, Dec 16, 2010 at 2:44 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> It's an indirect call to qemu_malloc, which never returns an error.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>
> v2:
> - Fixed bdrv_open failure case in xen_disk
>
> hw/xen_disk.c | 17 ++++++-----------
> qemu-img.c | 5 +----
> qemu-io.c | 2 --
> qemu-nbd.c | 2 --
> 4 files changed, 7 insertions(+), 19 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
prev parent reply other threads:[~2010-12-16 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 14:39 [Qemu-devel] [PATCH] Remove NULL checks for bdrv_new return value Kevin Wolf
2010-12-16 14:44 ` [Qemu-devel] [PATCH v2] " Kevin Wolf
2010-12-16 17:48 ` Stefan Hajnoczi [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=AANLkTimPYU1XSLDX_RGEbMReWORONa7YWn3r1ST4wGjo@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=kwolf@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).