Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1669197imm; Thu, 18 Oct 2018 02:05:06 -0700 (PDT) X-Google-Smtp-Source: ACcGV61us7mkmkf1BDF2hM77apg7gMxMx/uTv0Z63ddu6Mu9QEdN7/gowHgSt7ToTgZ/vEU63OjE X-Received: by 2002:a63:1302:: with SMTP id i2-v6mr28290990pgl.380.1539853506661; Thu, 18 Oct 2018 02:05:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539853506; cv=none; d=google.com; s=arc-20160816; b=vsgPXAQOZOPVU3knPeYlVfF+XX53HM5X5lr0mdD3domtzRAXXGbrMiUq+HC01criHk D7bguLZqHSCNUQC58uI0RkZWuBEZD1UWQWyEyTktQKm6t5vwkrWZ/xmYHNK0wQILpA/u R6TFJBVtyRUiQeYzAqyZhJbu0DDMqTTGZ/B3Xrykq//+pjAVRF8aBp3dMp9R+gZnAVqR uUJRS6dq9bRbrGX83M/qL7QRu5QU98WZ1zyX6P9F5dx543EiZLBPEZ+m1uSmedZtJYJx eoINvmuheN4ht0AXvD34RDwrk2ApJk0NG8+2NgURlM6BUlyW2nOIkY++M2WyD1Rwc11d acQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Ga/DkeCdUwZfuJ43M1AI7ml+U7aDfk4Ahy3YuQmnhzY=; b=pCaQxEH7rlm8Q96dAb7daOMJpgmOF9IvSN+7BVLUlcHJO9HLHdrNbt6cVyw/W1hCzC ZxuGCYT+oPnusiSZR1FXHsmRJsjZrIFjy8foYjhNIMI32z3do4wLR9u8Qu379EgfNND3 HNACEIDDUKm7maCXstI/JnW33WG36ueEjMNN+VwLETBKJwgDWwj8xLE8GsX7nTIhIC3v YeInMkTK2ZxuH1F+PAbY/PaAs3Ry5vqIb2G6EC7y+pBQoAauFozJa1k5usTrOUKdqtFp UUSPcHSmrSZZZ+Rny3RgatxRNmzGBRWdxOqzz50KHE+vh5SzlMh+eZX/twx8lnOdGOTQ VaRQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h128-v6si7789979pfc.165.2018.10.18.02.04.48; Thu, 18 Oct 2018 02:05:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728161AbeJRRD7 (ORCPT + 99 others); Thu, 18 Oct 2018 13:03:59 -0400 Received: from smtp2200-217.mail.aliyun.com ([121.197.200.217]:46768 "EHLO smtp2200-217.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727363AbeJRRD7 (ORCPT ); Thu, 18 Oct 2018 13:03:59 -0400 X-Alimail-AntiSpam: AC=CONTINUE;BC=0.0744096|-1;CH=green;FP=0|0|0|0|0|-1|-1|-1;HT=e01e01534;MF=ren_guo@c-sky.com;NM=1;PH=DS;RN=16;RT=16;SR=0;TI=SMTPD_---.D3u10GY_1539853403; Received: from localhost(mailfrom:ren_guo@c-sky.com fp:SMTPD_---.D3u10GY_1539853403) by smtp.aliyun-inc.com(10.147.42.197); Thu, 18 Oct 2018 17:03:23 +0800 Date: Thu, 18 Oct 2018 17:03:22 +0800 From: Guo Ren To: Arnd Bergmann Cc: Andrew Morton , Daniel Lezcano , David Miller , gregkh , Christoph Hellwig , Marc Zyngier , Mark Rutland , Peter Zijlstra , Rob Herring , Thomas Gleixner , Linux Kernel Mailing List , linux-arch , DTML , Rob Herring , c-sky_gcc_upstream@c-sky.com Subject: Re: [PATCH V9 00/21] C-SKY(csky) Linux Kernel Port Message-ID: <20181018090322.GB21934@guoren-Inspiron-7460> References: <20181018041038.GB17276@guoren-Inspiron-7460> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 18, 2018 at 10:36:45AM +0200, Arnd Bergmann wrote: > On Thu, Oct 18, 2018 at 6:11 AM Guo Ren wrote: > > > > On Wed, Oct 17, 2018 at 05:58:46PM +0200, Arnd Bergmann wrote: > > > On Tue, Oct 16, 2018 at 4:58 AM Guo Ren 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. > > Yes, it is always an option to make glibc more restrictive than the kernel. > We could also just make it a configuration option in the kernel whether > the system calls are provided, so they don't use memory for the > implementation. Ok. > You will probably want musl support at some point. musl-1.x always > uses 32-bit time_t today, but musl-2.x will use the 64-bit interfaces, > so just waiting a bit will probably make it work out for you. Thx for the tips, we'll consider musl in the future. Best Regards Guo Ren