On Mon, Sep 17, 2018 at 09:54:43PM +1000, Stephen Rothwell wrote: > Hi Guo, > > On Sun, 16 Sep 2018 12:53:26 +0800 Guo Ren <ren_guo@xxxxxxxxx> wrote: > > > > I'm Guo Ren from C-SKY and I'm working on csky linux port upstream. > > I've prepared my git-tree based on linux-4.19-rc3: > > git clone -b linux-next https://github.com/c-sky/csky-linux.git > > > > Here is the pre-built cross compiler for fast test from our CI: > > https://gitlab.com/c-sky/buildroot/-/jobs/97941896/artifacts/file/output/images/csky_toolchain_csky_ck860_platform_defconfig_72371bf75a51f27ea59fc34eeaf236e06b75bf69.tar.xz > > > > You can also build newest gcc, binutils and they are upstreamed but not > > released on gnu.org. Glibc is uptreaming now. > > > > Please have a look and any feed back is welcome. > > Added from today (called "csky"). > > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgement of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window. > > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, > * posted to the relevant mailing list, > * reviewed by you (or another maintainer of your subsystem tree), > * successfully unit tested, and > * destined for the current or next Linux merge window. > > Basically, this should be just what you would send to Linus (or ask him > to fetch). It is allowed to be rebased if you deem it necessary. I am very excited to receive your mail. I have been preparing for this for nearly 3 years. - All files are under GPL v2 - All Contributors have been Signed-off. - All have been reviewed. - For develop detail you can find in: https://github.com/c-sky/csky-linux It records from 'Dec 2015' to 'Sep 2018'. - Here is the newest ltp test result: https://gitlab.com/c-sky/buildroot/-/jobs/98061317 Best Regards Guo Ren
