From: Amit Shah <amit.shah@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: pbonzini@redhat.com, Ulrich Obergfell <uobergfe@redhat.com>,
qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] We should check virtio_load return code
Date: Thu, 1 Mar 2012 14:59:25 +0530 [thread overview]
Message-ID: <20120301092925.GD2903@amit.redhat.com> (raw)
In-Reply-To: <1330435867-17860-1-git-send-email-owasserm@redhat.com>
On (Tue) 28 Feb 2012 [15:31:07], Orit Wasserman wrote:
> Otherwise we crash on error.
A description on how to reproduce the crash would be nice.
> Signed-off-by: Orit Wasserman <owasserm@redhat.com>
> Signed-off-by: Ulrich Obergfell <uobergfe@redhat.com>
Acked-by: Amit Shah <amit.shah@redhat.com>
Amit
next prev parent reply other threads:[~2012-03-01 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 13:31 [Qemu-devel] [PATCH] We should check virtio_load return code Orit Wasserman
2012-02-28 13:40 ` Paolo Bonzini
2012-03-01 9:29 ` Amit Shah [this message]
2012-03-01 9:56 ` Markus Armbruster
2012-03-01 11:00 ` Orit Wasserman
2012-03-01 11:14 ` Paolo Bonzini
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=20120301092925.GD2903@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=uobergfe@redhat.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).