From: Stefan Hajnoczi <stefanha@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/vhdx: Error checking fixes
Date: Thu, 30 Jan 2014 10:34:19 +0100 [thread overview]
Message-ID: <20140130093419.GA15567@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1391015108-31808-1-git-send-email-armbru@redhat.com>
On Wed, Jan 29, 2014 at 06:05:08PM +0100, Markus Armbruster wrote:
> Errors are inadvertently ignored in a few places. Has always been
> broken. Spotted by Coverity.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> block/vhdx-log.c | 4 ++--
> block/vhdx.c | 8 ++++----
> 2 files changed, 6 insertions(+), 6 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2014-01-30 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 17:05 [Qemu-devel] [PATCH] block/vhdx: Error checking fixes Markus Armbruster
2014-01-29 17:14 ` Jeff Cody
2014-01-30 9:34 ` 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=20140130093419.GA15567@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.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).