From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
peter.maydell@linaro.org, doug16k@gmail.com,
imbrenda@linux.vnet.ibm.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] some gdbstub fixes for debug and vcont
Date: Mon, 5 Jun 2017 15:48:01 +0200 [thread overview]
Message-ID: <88a5d9d3-1827-2b31-b81a-f755da583f52@redhat.com> (raw)
In-Reply-To: <20170602130518.22943-1-alex.bennee@linaro.org>
On 02/06/2017 15:05, Alex Bennée wrote:
> Hi,
>
> This is v3 and hopefully the final version the gdbstub fixes. There is
> one minor change to patch two where I pulled forward the move of
> cpu_gdb_index into gdbstub.c from the third patch.
>
> Otherwise it is basically a re-base and a whole host of Reviewed-by
> tags.
>
> So the final question is who's tree is going to accept these patches?
>
> The gdbstub is currently marked as "Odd fixes" via qemu-devel. If no
> one wants to take it via their tree and Peter is happy I can roll the
> pullreq directly.
With pleasure (but I reported an issue on patch 3).
Thanks,
Paolo
prev parent reply other threads:[~2017-06-05 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:05 [Qemu-devel] [PATCH v3 0/4] some gdbstub fixes for debug and vcont Alex Bennée
2017-06-02 13:05 ` [Qemu-devel] [PATCH v3 1/4] gdbstub: modernise DEBUG_GDB Alex Bennée
2017-06-02 13:05 ` [Qemu-devel] [PATCH v3 2/4] gdbstub: rename cpu_index -> cpu_gdb_index Alex Bennée
2017-06-02 13:05 ` [Qemu-devel] [PATCH v3 3/4] qom/cpu: remove host_tid field Alex Bennée
2017-06-05 13:47 ` Paolo Bonzini
2017-06-05 15:10 ` Alex Bennée
2017-06-02 13:05 ` [Qemu-devel] [PATCH v3 4/4] gdbstub: don't fail on vCont; C04:0; c packets Alex Bennée
2017-06-05 20:56 ` Philippe Mathieu-Daudé
2017-06-05 13:48 ` Paolo Bonzini [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=88a5d9d3-1827-2b31-b81a-f755da583f52@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=doug16k@gmail.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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).