From: Stafford Horne <shorne@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Stafford Horne <shorne@gmail.com>,
gdb-patches@sourceware.org, openrisc@lists.librecores.org
Subject: Re: [PATCH 00/18] gdb: Port for OpenRISC
Date: Fri, 25 Nov 2016 22:50:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.20.1611260747470.29569@lianli.shorne-pla.net> (raw)
In-Reply-To: <20161124203629.gaokqfocdcev2zfq@localhost>
On Thu, 24 Nov 2016, Yao Qi wrote:
> On Thu, Nov 24, 2016 at 07:10:26AM +0900, Stafford Horne wrote:
>> Hello,
>>
>> 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. Other
>> are willing to do what it takes for FSF copyright assignment.
>>
>
> Hi Stafford,
> It is a new port in FSF GDB, and we want the quality of this new port is
> good enough, so the history of openrisc branch isn't very important in
> the patch review. Please put all or1k-tdep.{c,h} changes into a single
> patch, and the authors in the ChangeLog entry should be all the
> contributors to or1k-tdep.{c,h}. The target independent changes can
> still sit in each patch if necessary.
Thanks I am working on this. Getting the changelog fixed up is taking time
as not all authors over the years maintained this so well.
> Please look at https://sourceware.org/gdb/wiki/ContributionChecklist
Thanks this is helpful.
-Stafford
prev parent reply other threads:[~2016-11-25 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 22:11 Stafford Horne
2016-11-23 22:11 ` [PATCH 04/18] gdb: add tdesc_find_register functions Stafford Horne
2016-11-23 22:11 ` [PATCH 17/18] gdb: or1k: Updates for compiler type checking Stafford Horne
2016-11-23 22:11 ` [PATCH 13/18] gdb: Add OpenRISC to texinfo menu Stafford Horne
2016-11-23 22:11 ` [PATCH 05/18] gdb: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2016-11-23 22:11 ` [PATCH 09/18] gdb: or1k: Silence gcc warning Stafford Horne
2016-11-23 22:11 ` [PATCH 03/18] gdb: or1k: Add or1k_push_dummy_code and use it Stafford Horne
2016-11-23 22:11 ` [PATCH 16/18] gdb: Remove corelow object from or1k linux build Stafford Horne
2016-11-23 22:11 ` [PATCH 15/18] gdb: or1k: Update calling conventions to help pass tests Stafford Horne
2016-11-23 22:13 ` [PATCH 10/18] gdb: or1k: Fixes for things that broke after upstream merge Stafford Horne
2016-11-23 22:13 ` [PATCH 01/18] gdb: add or1k and or1knd target support Stafford Horne
2016-11-23 22:13 ` [PATCH 12/18] gdb: or1k: Apply changes of the last two years Stafford Horne
2016-11-23 22:13 ` [PATCH 08/18] gdb: or1k: change or1k_push_dummy_code stack alignment Stafford Horne
2016-11-23 22:14 ` [PATCH 14/18] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
2016-11-23 22:14 ` [PATCH 07/18] gdb: or1k: add target descriptor support Stafford Horne
2016-11-23 22:14 ` [PATCH 06/18] gdb: or1k: set gdbarch num regs to gpr + spr regs Stafford Horne
2016-11-23 22:16 ` [PATCH 02/18] gdb: or1k: Add a check for NULL ptr in or1k_skip_prologue Stafford Horne
2016-11-23 22:16 ` [PATCH 11/18] Add gdb for or1k build Stafford Horne
2016-11-23 22:23 ` [PATCH 18/18] gdb: or1k: Refactor to new bp_kind_from_pc and pb_from_kind Stafford Horne
2016-11-24 20:37 ` [PATCH 00/18] gdb: Port for OpenRISC Yao Qi
2016-11-25 22:50 ` 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=alpine.LFD.2.20.1611260747470.29569@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