From: Stafford Horne <shorne@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org, openrisc@lists.librecores.org
Subject: Re: [PATCH v5 0/4] OpenRISC gdb port
Date: Tue, 21 Mar 2017 14:17:00 -0000 [thread overview]
Message-ID: <20170321141739.GD2570@lianli.shorne-pla.net> (raw)
In-Reply-To: <86d1dbvvnr.fsf@gmail.com>
On Tue, Mar 21, 2017 at 09:14:32AM +0000, Yao Qi wrote:
> Stafford Horne <shorne@gmail.com> writes:
>
> > This is the openrisc port of GDB that has been in openrisc
> > repositories for a very long time. The main original author
> > was Jeremy Bennett as can be seen in file copyrights. Others
> > should also have copyright assignment in place.
>
> Hi Stafford,
> Thanks for the patches, but I don't have cycles to review them now,
> because of the 8.0 release. I'll review them after 8.0 release.
Understood,
Thanks for the heads up, I will post again after the 8.0 release. There
are a few changes I made after Eli's comments.
> --
> Yao (é½å°§)
prev parent reply other threads:[~2017-03-21 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 5:43 Stafford Horne
2017-03-17 5:43 ` [PATCH v5 4/4] Add gdb for or1k build Stafford Horne
2017-04-04 21:32 ` Yao Qi
2017-03-17 5:43 ` [PATCH v5 1/4] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2017-03-17 8:49 ` Eli Zaretskii
2017-03-17 9:32 ` Stafford Horne
2017-03-17 9:36 ` Eli Zaretskii
2017-03-17 10:03 ` Stafford Horne
2017-04-04 21:17 ` Yao Qi
2017-04-08 9:36 ` Stafford Horne
2017-03-17 5:43 ` [PATCH v5 3/4] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
2017-04-04 21:30 ` Yao Qi
2017-03-17 5:44 ` [PATCH v5 2/4] gdb: provide openrisc target description XML files Stafford Horne
2017-04-04 21:25 ` Yao Qi
2017-04-08 9:38 ` Stafford Horne
2017-03-21 9:14 ` [PATCH v5 0/4] OpenRISC gdb port Yao Qi
2017-03-21 14:17 ` Stafford Horne [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=20170321141739.GD2570@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=qiyaoltc@gmail.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