From: Mike Frysinger <vapier@gentoo.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 00/18] sim: port for OpenRISC
Date: Sat, 17 Dec 2016 23:33:28 -0500 [thread overview]
Message-ID: <20161218043328.GA9608@vapier.lan> (raw)
In-Reply-To: <20161217041836.GH2650@lianli.shorne-pla.net>
On 17 Dec 2016 13:18, Stafford Horne wrote:
> On Fri, Dec 16, 2016 at 03:34:21PM -0500, Mike Frysinger wrote:
> > On 05 Dec 2016 17:40, Stafford Horne wrote:
> > > On Sat, Nov 26, 2016 at 07:46:37AM +0900, Stafford Horne wrote:
> > > > On Fri, 25 Nov 2016, Mike Frysinger wrote:
> > > > > On 24 Nov 2016 07:14, Stafford Horne wrote:
> > > > > > The main author is Peter Gavin who should have his FSF copyright in place.
> > > > >
> > > > > what about yourself ? all authors should have papers in place.
> > > >
> > > > I do not yet, but I would like to. According to the gcc contributing
> > > > guidelines [1] it mentions:
> > > >
> > > > See some documentation by the FSF for details and contact us (either via
> > > > the gcc at gcc.gnu.org list or the GCC maintainer that is taking care of
> > > > your contributions) to obtain the relevant forms.
> > > >
> > > > I know this is not gcc, but gdb, but I thought it might be the same
> > > > process. Since it mentions 'via .. maintainer .. taking care of your ..' I
> > > > thought it best I submit these patches first.
> > > >
> > > > Could you send me the forms?
> > > >
> > > > [1] https://gcc.gnu.org/contribute.html
> > >
> > > I was able to get these forms submitted, but I may have made a mistake.
> > > Please, help clarify, I sent the program name as "GDB". However does
> > > that cover work on all of binutils-gdb? Or just gdb?
> >
> > i think each project is considered sep. you'll want binutils, gdb, and
> > sim. this is the form i used in the past (directions at the top):
> > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob_plain;f=doc/Copyright/request-assign.future;hb=HEAD
>
> Right, those are the same forms I used. I will additionally request sim
> and binutils.
thanks. let us know when it's sorted and we can start the review.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20161217/735ed721/attachment.sig>
prev parent reply other threads:[~2016-12-18 4:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 22:14 [OpenRISC] [PATCH 00/18] sim: port for OpenRISC Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 01/18] sim: cgen: add rem (remainder) function (needed for OR1K lf.rem.[sd]) Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 02/18] sim: cgen: add mul-o1flag, mul-o2flag RTL functions to CGEN Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 03/18] sim: cgen: allow suffix on generated arch.[ch] and cpuall.h Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 04/18] sim: or1k: add or1k target to sim Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 05/18] sim: or1k: add NOP_EXIT_SILENT; make simulator print exit code for NOP_EXIT; Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 06/18] sim: or1k: fix branching and exceptions in sim Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 07/18] sim: or1k: remove erroneous warning message in sim/or1k/or1k.c Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 08/18] sim: or1k: fix fl1 in sim Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 09/18] sim: or1k: regenerate sim files Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 10/18] sim: testsuite: add testsuite for or1k sim Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 11/18] sim: or1k: fix segfault when run without arguments Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 12/18] sim: or1k: Get or1k sim building with latest sim common Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 13/18] sim: or1k: Regenerate cgen files Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 14/18] sim: or1k: Regenerate autotool files Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 15/18] sim: or1k: Implement register store/fetch Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 16/18] sim: or1k: Do trap breakpoint handling Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 17/18] sim: or1k: Implement fetch/store for ppc and sr Stafford Horne
2016-11-23 22:14 ` [OpenRISC] [PATCH 18/18] sim: or1k: add additional stubs for linux build Stafford Horne
2016-11-23 23:04 ` [OpenRISC] [PATCH 00/18] sim: port for OpenRISC Stafford Horne
2016-11-25 16:19 ` Mike Frysinger
2016-11-25 22:46 ` Stafford Horne
2016-12-05 8:40 ` Stafford Horne
2016-12-16 20:34 ` Mike Frysinger
2016-12-17 4:18 ` Stafford Horne
2016-12-18 4:33 ` Mike Frysinger [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=20161218043328.GA9608@vapier.lan \
--to=vapier@gentoo.org \
--cc=openrisc@lists.librecores.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.