From: Yao Qi <qiyaoltc@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RISC-V GDB Port v3
Date: Tue, 21 Mar 2017 09:23:00 -0000 [thread overview]
Message-ID: <864lynvv9e.fsf@gmail.com> (raw)
In-Reply-To: <20170307043029.3672-1-palmer@dabbelt.com> (Palmer Dabbelt's message of "Mon, 6 Mar 2017 20:30:27 -0800")
Palmer Dabbelt <palmer@dabbelt.com> writes:
> I think the only thing I know of that's bad is the target XML description file,
> which I don't think works yet. That said, I want to send this patch set out
> just so we can all get on the same page.
>
> If I understand correctly, GDB-8 is set to be branched on the 15th so if I can
> fix up our port quickly we can still get it in?
Hi Palmer,
I don't have cycles reviewing the patches now, because of 8.0 release.
I can only offer some time after 8.0 release.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-03-21 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 20:31 Palmer Dabbelt
2017-03-06 20:31 ` [PATCH 1/2] RISC-V GDB Port Palmer Dabbelt
2017-04-04 21:48 ` Yao Qi
2017-04-24 16:12 ` Palmer Dabbelt
2017-04-05 9:22 ` Yao Qi
2017-03-06 20:31 ` [PATCH 2/2] RISC-V sim Port Palmer Dabbelt
2017-03-10 19:38 ` RISC-V GDB Port v3 Palmer Dabbelt
2017-03-21 9:23 ` Yao Qi [this message]
2017-03-21 16:04 ` Palmer Dabbelt
2017-04-05 9:30 ` 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=864lynvv9e.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.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