From: Tom Tromey <tom@tromey.com>
To: Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org>
Cc: Christina Schimpe <christina.schimpe@intel.com>,
tom@tromey.com, pedro@palves.net
Subject: Re: [PATCH v3 3/3] gdb: Remove workaround for the vCont packet
Date: Tue, 20 Dec 2022 13:29:34 -0700 [thread overview]
Message-ID: <87pmcdkedt.fsf@tromey.com> (raw)
In-Reply-To: <20220909153709.3687178-4-christina.schimpe@intel.com> (Christina Schimpe via Gdb-patches's message of "Fri, 9 Sep 2022 17:37:09 +0200")
>>>>> "Christina" == Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org> writes:
Christina> The workaround for the vCont packet is no longer required due to the
Christina> former commit "gdb: Make global feature array a per-remote target array".
Christina> The vCont packet is now checked once when the connection is started and
Christina> the supported vCont actions are set to the target's remote state
Christina> attribute.
Hi. I was curious, what's the status of this series?
Tom
next prev parent reply other threads:[~2022-12-20 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:37 [PATCH v3 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-09-09 15:37 ` [PATCH v3 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-10-04 13:48 ` Pedro Alves
2022-10-18 10:26 ` Schimpe, Christina
2022-09-09 15:37 ` [PATCH v3 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-09-09 15:57 ` Eli Zaretskii
2022-09-09 15:37 ` [PATCH v3 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2022-12-20 20:29 ` Tom Tromey [this message]
2022-12-21 7:42 ` Schimpe, Christina
2022-10-04 12:40 ` [PING][PATCH v3 0/3] Apply fixme notes for multi-target support Schimpe, Christina
2022-10-04 12:40 ` Schimpe, Christina
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=87pmcdkedt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).