linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Guo Ren <ren_guo@c-sky.com>
Cc: 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>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port
Date: Wed, 12 Sep 2018 16:30:36 +0200	[thread overview]
Message-ID: <CAK8P3a0CUYyMR9hDG97Zf2Oyj+D9vwQRnPZrEs0rrOLwHqxYfw@mail.gmail.com> (raw)
In-Reply-To: <cover.1536757532.git.ren_guo@c-sky.com>

On Wed, Sep 12, 2018 at 3:25 PM Guo Ren <ren_guo@c-sky.com> wrote:
>
> This is the 3th version patchset to add the Linux kernel port for C-SKY(csky).
> Thanks to everyone who provided feedback on the previous version.
>
> This patchset adds architecture support to Linux for C-SKY's 32-bit embedded
> CPU cores and the patches are based on linux-4.18.4
>
> There are two ABI versions with several CPU cores in this patchset:
>   ABIv1: ck610 (16-bit instruction, 32-bit data path, VIPT Cache ...)
>   ABIv2: ck807 ck810 ck860 (16/32-bit variable length instruction, PIPT Cache,
>          SMP ...)
>
> More information: http://en.c-sky.com

This looks good to me overall. I think a good next step would be to get the port
included in linux-next, by preparing a git tree with all the patches and asking
Stephen Rothwell to include it there. Further comments on the architecture
port itself can be done on top of the existing patches. I would suggest you
base the git tree on an -rc release (either 4.19-rc1 or 4.19-rc3) and then never
rebase again.

You have included a couple of drivers in the submission: two timer and
two irqchip drivers. Please leave those out for the moment, and either have
them merged through the respective subsystem  trees, or get an Ack
from the maintainers to merge them through your tree.

I notice that a lot of the patches have no changeset comments on them.
You should fix that and make a habit of describing every single patch
with a few sentences, even if it seems obvious to you. Have a look at
the changeset descriptions for the nds32 and riscv architectures when
they got merged.

One big question for me is what to do about time_t. Deepa and I are
in the process of finalizing the system call ABI for 32-bit architectures
with 64-bit time_t, but we are not done yet and it won't be complete
for 4.20. If you target 4.21, that could be a chance to make csky the
first architecture to only need the 64-bit time_t interface, with the
corresponding user space changes.

        Arnd

  parent reply	other threads:[~2018-09-12 14:30 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 ` Arnd Bergmann [this message]
2018-09-14 14:37   ` [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port 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
     [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=CAK8P3a0CUYyMR9hDG97Zf2Oyj+D9vwQRnPZrEs0rrOLwHqxYfw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=andrea.parri@amarulasolutions.com \
    --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=ren_guo@c-sky.com \
    --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).