On Fri, Sep 14, 2018 at 06:09:35PM +0200, Arnd Bergmann wrote: > On Fri, Sep 14, 2018 at 6:02 PM Guo Ren <ren_guo@xxxxxxxxx> 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 <ren_guo@xxxxxxxxx> 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
