From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv2 0/3] Additional maintenance command for dumping target descriptions
Date: Tue, 23 Jun 2020 14:58:13 +0100 [thread overview]
Message-ID: <3fcb3f92-3ac0-64bf-1047-67f72f416454@redhat.com> (raw)
In-Reply-To: <20200622181304.GM2737@embecosm.com>
Hi Andrew,
On 6/22/20 7:13 PM, Andrew Burgess wrote:
> Pedro,
>
> I wonder if you have any feedback on the changes in this version?
> Specifically with how I now handle the 'compatibility' tags in a way
> that allows the code to be shared between gdbserver and gdb?
>
I commented on a commit log typo on patch #3, but otherwise
this all LGTM. Thanks for confirming.
Pedro Alves
prev parent reply other threads:[~2020-06-23 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 23:22 Andrew Burgess
2020-06-11 23:22 ` [PATCHv2 1/3] gdb: Allow target description to be dumped even when it is remote Andrew Burgess
2020-06-11 23:22 ` [PATCHv2 2/3] gdb: Print compatible information within print_xml_feature Andrew Burgess
2020-06-11 23:22 ` [PATCHv2 3/3] gdb: New maintenance command to print XML target description Andrew Burgess
2020-06-23 13:48 ` Pedro Alves
2020-06-22 18:13 ` [PATCHv2 0/3] Additional maintenance command for dumping target descriptions Andrew Burgess
2020-06-23 13:58 ` Pedro Alves [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=3fcb3f92-3ac0-64bf-1047-67f72f416454@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).