Re: [PATCH v2] RISC-V: Support for FreeBSD

2018-04-06 Thread Jim Wilson
On Thu, Apr 5, 2018 at 8:48 PM, Kito Cheng wrote: > Theodore Teah sent an mail say "Your assignment/disclaimer process > with the FSF is currently complete.". > > Could you help us to commit that? Committed. With some riscv{32,64}-{elf,linux,freebsd} cross compiler build tests, to make sure the

Re: [PATCH v2] RISC-V: Support for FreeBSD

2018-04-05 Thread Kito Cheng
Hi Jim: Theodore Teah sent an mail say "Your assignment/disclaimer process with the FSF is currently complete.". Could you help us to commit that? Thanks :) On Fri, Feb 23, 2018 at 2:33 AM, Jim Wilson wrote: > On Wed, Feb 21, 2018 at 10:34 PM, Kito Cheng wrote: >> I don't family with copyrigh

Re: [PATCH v2] RISC-V: Support for FreeBSD

2018-02-22 Thread Jim Wilson
On Wed, Feb 21, 2018 at 10:34 PM, Kito Cheng wrote: > I don't family with copyright matters, so we can't commit this patch yet > until Ruslan send the signed copy and FSF signed it? right? Yes, I'd prefer that the FSF sign it and add it to the copyright list before we commit the patch. Jim

Re: [PATCH v2] RISC-V: Support for FreeBSD

2018-02-21 Thread Kito Cheng
Hi Jim: > I saw the email. I checked the FSF copyright list and see that it > hasn't been recorded yet. The FSF copyright clerk sometimes takes a > few weeks to respond. Hopefully this will be competed on the FSF side > soon. I don't family with copyright matters, so we can't commit this patch

Re: [PATCH v2] RISC-V: Support for FreeBSD

2018-02-20 Thread Jim Wilson
On Sat, Feb 17, 2018 at 7:08 PM, Kito Cheng wrote: > Hi all: > > This patch is version 2 of FreeBSD supporting for RISC-V, Ruslan > (RISC-V FreeBSD maintainer) and me has been tested on FreeBSD 12 > for building kernel and whole user space programs/libraries again :) This looks OK. > Copyright p

[PATCH v2] RISC-V: Support for FreeBSD

2018-02-17 Thread Kito Cheng
Hi all: This patch is version 2 of FreeBSD supporting for RISC-V, Ruslan (RISC-V FreeBSD maintainer) and me has been tested on FreeBSD 12 for building kernel and whole user space programs/libraries again :) Hi Jim: Ruslan and me just decide upstream GCC part only this time since binutils need m