From: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, palves@redhat.com, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont
Date: Thu, 12 Jan 2017 17:45:01 +0100 [thread overview]
Message-ID: <08201dc9-c077-feee-14e1-a8f0f225b9d7@linux.vnet.ibm.com> (raw)
In-Reply-To: <1477674916-6795-1-git-send-email-imbrenda@linux.vnet.ibm.com>
Hello,
just a respectful poke to remind about this patchset :)
Claudio
next prev parent reply other threads:[~2017-01-12 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 17:15 [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2016-10-28 17:15 ` [Qemu-devel] [PATCH v3 1/2] move vm_start to cpus.c Claudio Imbrenda
2017-01-25 10:21 ` Paolo Bonzini
2017-01-25 17:53 ` Claudio Imbrenda
2017-01-25 18:02 ` Paolo Bonzini
2016-10-28 17:15 ` [Qemu-devel] [PATCH v3 2/2] gdbstub: Fix vCont behaviour Claudio Imbrenda
2017-01-25 10:34 ` Paolo Bonzini
2017-01-25 17:55 ` Claudio Imbrenda
2016-11-30 15:37 ` [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2017-01-12 16:45 ` Claudio Imbrenda [this message]
2017-01-25 10:05 ` Christian Borntraeger
2017-01-25 10:12 ` 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=08201dc9-c077-feee-14e1-a8f0f225b9d7@linux.vnet.ibm.com \
--to=imbrenda@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=palves@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).