From: Guo Ren <ren_guo@c-sky.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
David Miller <davem@davemloft.net>,
gregkh <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@infradead.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
c-sky_gcc_upstream@c-sky.com
Subject: Re: [PATCH V9 00/21] C-SKY(csky) Linux Kernel Port
Date: Thu, 18 Oct 2018 12:10:51 +0800 [thread overview]
Message-ID: <20181018041038.GB17276@guoren-Inspiron-7460> (raw)
In-Reply-To: <CAK8P3a25W5rE093QsmC539d+s038Wv9PmV8Xa76LQzDLk3E8Wg@mail.gmail.com>
On Wed, Oct 17, 2018 at 05:58:46PM +0200, Arnd Bergmann wrote:
> On Tue, Oct 16, 2018 at 4:58 AM Guo Ren <ren_guo@c-sky.com> wrote:
> >
> > This is the 9th version patchset to add the Linux kernel port for
> > C-SKY(csky) based on linux-4.19-rc3.
> >
> > There are only a few changes between V8 patchset. Hope it could be
> > merged into linux-4.20 and I'm very grateful for any help.
>
> I've gone through the entire series once more and saw no show-stoppers.
> The last patch looked like it introduced a bug, but with that one dropped,
> I'm happy for the architecture to get merged, unless anyone else
> has any last-minute concerns. (Alternatively, explain why I'm wrong
> and the code works correctly, of course).
Ok and thx for the job of csky subsystem.
>
> I'd appreciate having someone else take another look at the signal
> handling code, the atomics, and the DT bindings and provide another
> Ack for those.
>
> The remaining open question is about the 32-bit time_t interfaces.
> With 4.20, I did not manage to get the required system calls in place
> for using 64-bit time_t in a new architecture, so you will at least
> start out using 32-bit time_t and likely have to keep supporting
> that going forward, unless we decide to break the ABI here later
> on .This is something we normally don't do, but we might make
> an exception here, under the assumption that there are no
> existing users with the ABI. We can debate that once we get there.
We support uclibc-ng and glibc.
1. For uclibc-ng, linux-4.20 could run with it.
2. For glibc, Maybe we could support 32-bit + 64-bit time_t with
KERNEL_VERSION, or just only 64-bit then linux-4.20 couldn't work with
the csky first glibc release.
Best Regards
Guo Ren
next prev parent reply other threads:[~2018-10-18 4:11 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 2:58 [PATCH V9 00/21] C-SKY(csky) Linux Kernel Port Guo Ren
2018-10-16 2:58 ` [PATCH V9 01/21] csky: Build infrastructure Guo Ren
2018-10-23 0:08 ` Guo Ren
2018-10-24 22:53 ` Arnd Bergmann
2018-10-25 17:04 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 02/21] csky: defconfig Guo Ren
2018-10-17 14:56 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 03/21] csky: Kernel booting Guo Ren
2018-10-17 14:58 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 04/21] csky: Exception handling and mm-fault Guo Ren
2018-10-17 14:59 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 05/21] csky: System Call Guo Ren
2018-10-17 15:02 ` Arnd Bergmann
2018-10-18 2:02 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 06/21] csky: Cache and TLB routines Guo Ren
2018-10-17 15:08 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 07/21] csky: MMU and page table management Guo Ren
2018-10-17 15:06 ` Arnd Bergmann
2018-10-18 2:05 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 08/21] csky: Process management and Signal Guo Ren
2018-10-17 15:11 ` Arnd Bergmann
2018-10-18 2:37 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 09/21] csky: VDSO and rt_sigreturn Guo Ren
2018-10-17 15:13 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 10/21] csky: IRQ handling Guo Ren
2018-10-17 15:14 ` Arnd Bergmann
2018-10-18 2:39 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 11/21] csky: Atomic operations Guo Ren
2018-10-17 15:17 ` Arnd Bergmann
2018-10-18 2:40 ` Guo Ren
2018-10-21 20:55 ` Peter Zijlstra
2018-10-22 1:52 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 12/21] csky: ELF and module probe Guo Ren
2018-10-17 15:18 ` Arnd Bergmann
2018-10-18 2:49 ` Guo Ren
2018-10-18 8:31 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 13/21] csky: Library functions Guo Ren
2018-10-17 15:24 ` Arnd Bergmann
2018-10-18 3:10 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 14/21] csky: User access Guo Ren
2018-10-17 15:37 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 15/21] csky: Debug and Ptrace GDB Guo Ren
2018-10-17 15:46 ` Arnd Bergmann
2018-10-18 3:17 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 16/21] csky: SMP support Guo Ren
2018-10-17 15:47 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 17/21] csky: Misc headers Guo Ren
2018-10-17 15:49 ` Arnd Bergmann
2018-10-16 2:58 ` [PATCH V9 18/21] dt-bindings: csky CPU Bindings Guo Ren
2018-10-17 15:50 ` Arnd Bergmann
2018-10-18 3:21 ` Guo Ren
2018-10-18 3:45 ` Guo Ren
2018-10-18 14:31 ` Rob Herring
2018-10-19 2:19 ` Guo Ren
2018-10-16 2:58 ` [PATCH V9 19/21] dt-bindings: Add vendor prefix for csky Guo Ren
2018-10-16 2:58 ` [PATCH V9 20/21] MAINTAINERS: Add csky Guo Ren
2018-10-17 15:51 ` Arnd Bergmann
2018-10-16 5:48 ` [PATCH V9 21/21] csky: support dword access for get_user_size() Guo Ren
2018-10-17 15:44 ` Arnd Bergmann
2018-10-18 3:41 ` Guo Ren
2018-10-18 8:34 ` Arnd Bergmann
2018-10-18 8:57 ` Guo Ren
2018-10-24 7:17 ` Arnd Bergmann
2018-10-25 17:08 ` Guo Ren
2018-10-17 15:58 ` [PATCH V9 00/21] C-SKY(csky) Linux Kernel Port Arnd Bergmann
2018-10-18 4:10 ` Guo Ren [this message]
2018-10-18 8:36 ` Arnd Bergmann
2018-10-18 9:03 ` 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=20181018041038.GB17276@guoren-Inspiron-7460 \
--to=ren_guo@c-sky.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=c-sky_gcc_upstream@c-sky.com \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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).