From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] gdbstub runstate check follow-ups
Date: Mon, 3 Jun 2013 11:26:54 -0400 [thread overview]
Message-ID: <20130603112654.3111e1d0@redhat.com> (raw)
In-Reply-To: <1370272015-9659-1-git-send-email-pbonzini@redhat.com>
On Mon, 3 Jun 2013 17:06:53 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> My patch committed at 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc
> was broken. These patches fix the problem in a better way.
Looks good to me:
Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>
next prev parent reply other threads:[~2013-06-03 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 15:06 [Qemu-devel] [PATCH 0/2] gdbstub runstate check follow-ups Paolo Bonzini
2013-06-03 15:06 ` [Qemu-devel] [PATCH 1/2] gdbstub: fix for commit 87f25c12bfeaaa0c41fb857713bbc7e8a9b757dc Paolo Bonzini
2013-06-03 15:06 ` [Qemu-devel] [PATCH 2/2] gdbstub: let the debugger resume from guest panicked state Paolo Bonzini
2013-06-03 15:26 ` Luiz Capitulino [this message]
2013-06-07 23:33 ` [Qemu-devel] [PATCH 0/2] gdbstub runstate check follow-ups Andreas Färber
2013-06-10 21:48 ` Anthony Liguori
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=20130603112654.3111e1d0@redhat.com \
--to=lcapitulino@redhat.com \
--cc=lersek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.