From: Eli Zaretskii <eliz@gnu.org>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com, pedro@palves.net,
aburgess@redhat.com
Subject: Re: [PATCH v4 2/3] gdb: Add per-remote target variables for memory read and write config
Date: Wed, 21 Dec 2022 16:13:31 +0200 [thread overview]
Message-ID: <83pmccalpw.fsf@gnu.org> (raw)
In-Reply-To: <20221221133958.2111768-3-christina.schimpe@intel.com> (message from Christina Schimpe on Wed, 21 Dec 2022 14:39:57 +0100)
> From: Christina Schimpe <christina.schimpe@intel.com>
> Cc: tom@tromey.com,
> pedro@palves.net,
> aburgess@redhat.com,
> eliz@gnu.org,
> Christina Schimpe <christina.schimpe@intel.com>
> Date: Wed, 21 Dec 2022 14:39:57 +0100
>
> gdb/NEWS | 11 +-
> gdb/doc/gdb.texinfo | 15 +++
> gdb/remote.c | 163 +++++++++++++++++++++---------
> gdb/testsuite/gdb.base/remote.exp | 45 +++++----
> 4 files changed, 169 insertions(+), 65 deletions(-)
The documentation parts are OK, thanks.
next prev parent reply other threads:[~2022-12-21 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 13:39 [PATCH v4 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-12-21 13:39 ` [PATCH v4 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-12-21 14:08 ` Eli Zaretskii
2023-01-23 17:42 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina
2022-12-21 13:39 ` [PATCH v4 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-12-21 14:13 ` Eli Zaretskii [this message]
2023-01-23 17:43 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina
2022-12-21 13:39 ` [PATCH v4 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2023-01-23 17:46 ` Pedro Alves
2023-01-30 14:35 ` Schimpe, Christina
2023-01-16 8:58 ` [PING][PATCH v4 0/3] Apply fixme notes for multi-target support 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=83pmccalpw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.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 read-only IMAP folder(s) and NNTP newsgroup(s).