From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guo Ren Subject: Re: [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port Date: Sat, 15 Sep 2018 07:28:26 +0800 Message-ID: <20180914232826.GA1497@guoren-Inspiron-7460> References: <20180914143719.GA27689@guoren-Inspiron-7460> <20180914160231.GA32161@guoren-Inspiron-7460> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Arnd Bergmann Cc: linux-arch , Linux Kernel Mailing List , Thomas Gleixner , Daniel Lezcano , Jason Cooper , DTML , andrea.parri@amarulasolutions.com, Peter Zijlstra , c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, Thomas Petazzoni , wbx@uclibc-ng.org, Greentime Hu , Stephen Rothwell List-Id: linux-arch.vger.kernel.org On Fri, Sep 14, 2018 at 06:09:35PM +0200, Arnd Bergmann wrote: > On Fri, Sep 14, 2018 at 6:02 PM Guo Ren wrote: > > > > On Fri, Sep 14, 2018 at 04:46:56PM +0200, Arnd Bergmann wrote: > > > On Fri, Sep 14, 2018 at 4:37 PM Guo Ren wrote: > > > > > One level below that, you can of course choose to build > > > a distro with only 64-bit time_t regardless of whether there > > > is still support for 32-bit time_t in kernel and glibc or not. > > Do you mean I could merge kernel port into linux-4.19 or linux-4.20. > > But let glibc merged after linux-4.21 and csky glibc only support > > time64 syscalls ? > > Yes, that's what I meant. Note that it won't get merged into 4.19: > the merge window for that was after the 4.18 release and no > new features are getting merged for 4.19 that have not made it > into 4.19-rc1 already. > > Getting your code into linux-next now is the prerequisite for you > sending a pull request during the 4.20 window. Got it, thank you very much. Guo Ren From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2200-217.mail.aliyun.com ([121.197.200.217]:42560 "EHLO smtp2200-217.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725198AbeIOEpm (ORCPT ); Sat, 15 Sep 2018 00:45:42 -0400 Date: Sat, 15 Sep 2018 07:28:26 +0800 From: Guo Ren Subject: Re: [PATCH V4 00/27] C-SKY(csky) Linux Kernel Port Message-ID: <20180914232826.GA1497@guoren-Inspiron-7460> References: <20180914143719.GA27689@guoren-Inspiron-7460> <20180914160231.GA32161@guoren-Inspiron-7460> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Arnd Bergmann Cc: linux-arch , Linux Kernel Mailing List , Thomas Gleixner , Daniel Lezcano , Jason Cooper , DTML , andrea.parri@amarulasolutions.com, Peter Zijlstra , c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, Thomas Petazzoni , wbx@uclibc-ng.org, Greentime Hu , Stephen Rothwell Message-ID: <20180914232826._3CkfBlVOr03PSVSqSWTCP9PflNVTfdr4fty6KK7l2M@z> On Fri, Sep 14, 2018 at 06:09:35PM +0200, Arnd Bergmann wrote: > On Fri, Sep 14, 2018 at 6:02 PM Guo Ren wrote: > > > > On Fri, Sep 14, 2018 at 04:46:56PM +0200, Arnd Bergmann wrote: > > > On Fri, Sep 14, 2018 at 4:37 PM Guo Ren wrote: > > > > > One level below that, you can of course choose to build > > > a distro with only 64-bit time_t regardless of whether there > > > is still support for 32-bit time_t in kernel and glibc or not. > > Do you mean I could merge kernel port into linux-4.19 or linux-4.20. > > But let glibc merged after linux-4.21 and csky glibc only support > > time64 syscalls ? > > Yes, that's what I meant. Note that it won't get merged into 4.19: > the merge window for that was after the 4.18 release and no > new features are getting merged for 4.19 that have not made it > into 4.19-rc1 already. > > Getting your code into linux-next now is the prerequisite for you > sending a pull request during the 4.20 window. Got it, thank you very much. Guo Ren