Re: [Y2038] [RFC v2] vfs 64 bit time transition proposals

2016-02-24 Thread Julia Lawall
On Wed, 24 Feb 2016, Thomas Gleixner wrote: > On Fri, 12 Feb 2016, Arnd Bergmann wrote: > > Regarding the three versions, I think all of them are doable > > doable, and they all have their upsides and downsides but no > > showstoppers. > > > > Let me summarize what I see in the patches: > > > >

Re: [Y2038] [RFC v2] vfs 64 bit time transition proposals

2016-02-24 Thread Thomas Gleixner
On Fri, 12 Feb 2016, Arnd Bergmann wrote: > Regarding the three versions, I think all of them are doable > doable, and they all have their upsides and downsides but no > showstoppers. > > Let me summarize what I see in the patches: > > 2a is the smallest set of changes in number of lines, as you

Re: [Y2038] [RFC v2] vfs 64 bit time transition proposals

2016-02-12 Thread Arnd Bergmann
On Friday 12 February 2016 01:21:59 Deepa Dinamani wrote: > Introduction > > This is a follow on to the series: https://lkml.org/lkml/2016/1/7/20 [1]. > This is aimed at reaching a consensus on how to transition the vfs > timestamps to use 64 bit time. This demonstrates three ways (2a, 2b and >

Re: [Y2038] [RFC v2] vfs 64 bit time transition proposals

2016-02-12 Thread Deepa Dinamani
> Regarding the three versions, I think all of them are doable > doable, and they all have their upsides and downsides but no > showstoppers. I agree that all the approaches are doable. > Let me summarize what I see in the patches: > > 2a is the smallest set of changes in number of lines, as you