From: Yan-Ting Lin <currygt52@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] AndesTech NDS32 port
Date: Tue, 10 May 2016 09:31:00 -0000 [thread overview]
Message-ID: <CAF3YKGNfXMXO3xjTDnJSmHO-cSF-hdvmDHYoUCKMM7oUo9+GvQ@mail.gmail.com> (raw)
In-Reply-To: <e65af384-a6e2-961d-e270-4decfcdab7c7@redhat.com>
Thanks for the review.
2016-05-10 2:33 GMT+08:00 Pedro Alves <palves@redhat.com>:
> On 05/05/2016 08:16 AM, Yan-Ting Lin wrote:
>> +<feature name="org.gnu.gdb.nds32.core">
>
> tdesc features need to be documented in the manual.
I am preparing this part. The documentation will be added at the next patch.
>
>> + register_remote_support_xml ("nds32");
>
> Is there a reason you needed this?
It is originally used to indicate NDS32 port support XML target
description for the different stubs.
After all stubs are modified to support this feature, this call can be removed.
I will remove this at the next patch.
>
> Thanks,
> Pedro Alves
>
next prev parent reply other threads:[~2016-05-10 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:16 Yan-Ting Lin
2016-05-05 23:46 ` Kevin Buettner
2016-05-06 11:00 ` Yao Qi
2016-05-06 16:09 ` Kevin Buettner
2016-05-09 8:15 ` Yao Qi
2016-05-10 8:45 ` Yan-Ting Lin
2016-05-09 18:33 ` Pedro Alves
2016-05-10 9:31 ` Yan-Ting Lin [this message]
2016-05-15 9:39 ` Yan-Ting Lin
2016-06-01 11:28 ` Yao Qi
2016-06-06 15:13 ` Yan-Ting Lin
2016-06-07 15:34 ` Yao Qi
2016-06-07 16:30 ` Eli Zaretskii
2016-06-08 8:17 ` Yao Qi
2016-06-17 8:08 ` Yan-Ting Lin
2016-06-13 14:12 ` Pedro Alves
2016-06-15 8:44 ` Yan-Ting Lin
2016-06-15 10:07 ` Pedro Alves
2016-06-01 10:52 ` Yao Qi
2016-06-01 11:00 ` Yao Qi
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=CAF3YKGNfXMXO3xjTDnJSmHO-cSF-hdvmDHYoUCKMM7oUo9+GvQ@mail.gmail.com \
--to=currygt52@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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