linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guo Ren <ren_guo@c-sky.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-arch <linux-arch@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Jason Cooper <jason@lakedaemon.net>,
	DTML <devicetree@vger.kernel.org>,
	andrea.parri@amarulasolutions.com,
	Peter Zijlstra <peterz@infradead.org>,
	c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	wbx@uclibc-ng.org, Greentime Hu <green.hu@gmail.com>
Subject: Re: [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port
Date: Mon, 17 Sep 2018 22:37:59 +0800	[thread overview]
Message-ID: <20180917143759.GA2612@guoren-Inspiron-7460> (raw)
In-Reply-To: <20180917215443.3b5808c5@canb.auug.org.au>

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@c-sky.com> 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

  parent reply	other threads:[~2018-09-17 14:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 13:24 [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port Guo Ren
2018-09-12 13:24 ` [PATCH V3 01/27] csky: Build infrastructure Guo Ren
2018-09-12 13:24 ` [PATCH V3 02/27] csky: defconfig Guo Ren
2018-09-12 13:24 ` [PATCH V3 03/27] csky: Kernel booting Guo Ren
2018-09-12 13:24 ` [PATCH V3 04/27] csky: Exception handling Guo Ren
2018-09-12 13:24 ` [PATCH V3 05/27] csky: System Call Guo Ren
2018-09-12 13:24 ` [PATCH V3 06/27] csky: Cache and TLB routines Guo Ren
2018-09-12 13:24 ` [PATCH V3 07/27] csky: MMU and page table management Guo Ren
2018-09-12 13:24 ` [PATCH V3 08/27] csky: Process management and Signal Guo Ren
2018-09-12 13:24 ` [PATCH V3 09/27] csky: VDSO and rt_sigreturn Guo Ren
2018-09-12 13:24 ` [PATCH V3 10/27] csky: IRQ handling Guo Ren
2018-09-12 13:24 ` [PATCH V3 12/27] csky: ELF and module probe Guo Ren
2018-09-12 13:24 ` [PATCH V3 13/27] csky: Library functions Guo Ren
2018-09-12 13:24 ` [PATCH V3 14/27] csky: User access Guo Ren
2018-09-12 13:24 ` [PATCH V3 15/27] csky: Debug and Ptrace GDB Guo Ren
2018-09-12 13:24 ` [PATCH V3 16/27] csky: SMP support Guo Ren
2018-09-12 13:24 ` [PATCH V3 18/27] dt-bindings: csky CPU Bindings Guo Ren
2018-09-12 13:24 ` [PATCH V3 19/27] dt-bindings: timer: gx6605s SOC timer Guo Ren
2018-09-12 13:24 ` [PATCH V3 20/27] dt-bindings: timer: C-SKY Multi-processor timer Guo Ren
2018-09-12 13:24 ` [PATCH V3 22/27] dt-bindings: interrupt-controller: C-SKY SMP intc Guo Ren
2018-09-12 13:24 ` [PATCH V3 23/27] clocksource: add gx6605s SOC system timer Guo Ren
     [not found] ` <abb46d366b513b814f7af234d560306a818b7324.1536757532.git.ren_guo@c-sky.com>
2018-09-12 14:22   ` [PATCH V3 17/27] csky: Misc headers Arnd Bergmann
2018-09-12 14:30 ` [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port Arnd Bergmann
2018-09-14 14:37   ` Guo Ren
2018-09-14 14:46     ` Arnd Bergmann
2018-09-14 16:02       ` Guo Ren
2018-09-14 16:09         ` Arnd Bergmann
2018-09-14 23:28           ` Guo Ren
2018-09-20 17:52     ` Palmer Dabbelt
2018-09-21  5:18       ` Arnd Bergmann
2018-09-21 23:48         ` Guo Ren
2018-09-24  7:21         ` Geert Uytterhoeven
2018-09-24  8:47           ` Arnd Bergmann
2018-09-16  1:07   ` Guo Ren
2018-09-16  4:53   ` Guo Ren
2018-09-17 11:54     ` Stephen Rothwell
2018-09-17 12:03       ` Stephen Rothwell
2018-09-17 14:50         ` Guo Ren
2018-09-17 14:37       ` Guo Ren [this message]
     [not found] ` <93e8b592e429c156ad4d4ca5d85ef48fd0ab8b70.1536757532.git.ren_guo@c-sky.com>
2018-09-12 15:55   ` [PATCH V3 11/27] csky: Atomic operations Peter Zijlstra
2018-09-15 14:55     ` Guo Ren
2018-09-17  8:17       ` Peter Zijlstra
2018-09-17 15:05         ` Guo Ren

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=20180917143759.GA2612@guoren-Inspiron-7460 \
    --to=ren_guo@c-sky.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=arnd@arndb.de \
    --cc=c-sky_gcc_upstream@c-sky.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gnu-csky@mentor.com \
    --cc=green.hu@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@uclibc-ng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).