From: Eli Zaretskii <eliz@gnu.org>
To: Youling Tang <tangyouling@loongson.cn>
Cc: gdb-patches@sourceware.org, macro@orcam.me.uk
Subject: Re: [PATCH] gdbserver: Add LoongArch/Linux port support
Date: Tue, 31 May 2022 14:22:18 +0300 [thread overview]
Message-ID: <83zgiyhrpx.fsf@gnu.org> (raw)
In-Reply-To: <1653965142-17332-1-git-send-email-tangyouling@loongson.cn> (message from Youling Tang on Tue, 31 May 2022 10:45:42 +0800)
> From: Youling Tang <tangyouling@loongson.cn>
> Date: Tue, 31 May 2022 10:45:42 +0800
> Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>
>
> 2022-05-31 Youling Tang <tangyouling@loongson.cn>
>
> gdb/
> * NEWS: Mention LoongArch GNU/Linux GDBserver support.
> * arch/loongarch.h: Declare the loongarch_create_target_description
> function when GDBSERVER is defined.
>
> gdbserver/
> * linux-loongarch-low.cc: New file.
> * Makefile.in (SFILES): Add linux-loongarch-low.cc and
> arch/loongarch.c.
> * configure.srv <loongarch*-*-linux*> (srv_tgtobj)
> srv_linux_regsets, srv_linux_usrregs, srv_linux_thread_db):
> Define.
OK for the NEWS part.
Thanks.
prev parent reply other threads:[~2022-05-31 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 2:45 Youling Tang
2022-05-31 11:22 ` Eli Zaretskii [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=83zgiyhrpx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=tangyouling@loongson.cn \
/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).