From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, Joel Stanley <joel@jms.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>,
alex.bennee@linaro.org,
Matheus Tavares Bernardino <quic_mathbern@quicinc.com>,
fbarrat@linux.ibm.com, qemu-devel@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [PATCH] gdbstub: Fix client Ctrl-C handling
Date: Tue, 1 Aug 2023 22:05:25 +0200 [thread overview]
Message-ID: <4bc9c439-4648-07f7-dd70-92828e006e5f@linaro.org> (raw)
In-Reply-To: <CAFEAcA-oB2U=eTzRqdHJVw2DZWPEnR_tS3M_+=yiF5GHtv_3tw@mail.gmail.com>
On 31/7/23 15:59, Peter Maydell wrote:
> On Mon, 31 Jul 2023 at 07:59, Joel Stanley <joel@jms.id.au> wrote:
>>
>> On Sun, 30 Jul 2023 at 09:43, Nicholas Piggin <npiggin@gmail.com> wrote:
>>>
>>> On Wed Jul 26, 2023 at 4:35 PM AEST, Joel Stanley wrote:
>>>> On Wed, 12 Jul 2023 at 02:12, Nicholas Piggin <npiggin@gmail.com> wrote:
>>>> I was taking a look at -rc1 and it looks like this hasn't made it in.
>>>> Is it something we want to propose including?
>>>>
>>>> As a user of qemu I'd vote for it to go in.
>>>
>>> I think it should, gdb is hardly usable without it.
>>
>> I think I hit this issue when debugging u-boot in the aspeed arm
>> machines. Your patch fixed things:
>>
>> Tested-by: Joel Stanley <joel@jms.id.au>
>>
>> Alex, Philippe, can we get this queued for 8.1?
>
> I'm doing a pullreq today anyway, so I can grab it.
Thank you Peter!
next prev parent reply other threads:[~2023-08-01 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:59 [PATCH] gdbstub: Fix client Ctrl-C handling Nicholas Piggin
2023-07-11 11:03 ` Matheus Tavares Bernardino
2023-07-12 2:11 ` Nicholas Piggin
2023-07-26 6:35 ` Joel Stanley
2023-07-30 9:43 ` Nicholas Piggin
2023-07-31 6:58 ` Joel Stanley
2023-07-31 13:59 ` Peter Maydell
2023-08-01 20:05 ` Philippe Mathieu-Daudé [this message]
2023-08-01 18:40 ` Matheus Tavares Bernardino
2023-08-08 22:56 ` Richard Henderson
2023-08-10 10:05 ` Alex Bennée
2023-07-12 2:13 ` Nicholas Piggin
2023-07-12 10:39 ` Michael Tokarev
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=4bc9c439-4648-07f7-dd70-92828e006e5f@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=fbarrat@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=npiggin@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quic_mathbern@quicinc.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).