Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder

2014-08-13 Thread Arnd Bergmann
On Tuesday 12 August 2014 20:45:03 John Stultz wrote: > On 08/12/2014 06:33 PM, j...@joshtriplett.org wrote: > > On Tue, Aug 12, 2014 at 05:08:53PM -0700, John Stultz wrote: > >> Also, just to clarify, as time related discussions can bring out a laundry > >> list of issues, I would like to focus th

Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder

2014-08-13 Thread Catalin Marinas
On Wed, Aug 13, 2014 at 02:37:11AM +0100, Andy Lutomirski wrote: > On Tue, Aug 12, 2014 at 6:33 PM, wrote: > > On Tue, Aug 12, 2014 at 05:08:53PM -0700, John Stultz wrote: > >> A more aggressive version of the previous proposal is what I’m calling the > >> “New Virtual-Architecture” approach, bas

Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder

2014-08-12 Thread John Stultz
On 08/12/2014 06:33 PM, j...@joshtriplett.org wrote: > On Tue, Aug 12, 2014 at 05:08:53PM -0700, John Stultz wrote: >> Also, just to clarify, as time related discussions can bring out a laundry >> list of issues, I would like to focus this discussion on providing a 2038 >> solution for existing int

Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder

2014-08-12 Thread Andy Lutomirski
On Tue, Aug 12, 2014 at 6:33 PM, wrote: > On Tue, Aug 12, 2014 at 05:08:53PM -0700, John Stultz wrote: >> Also, just to clarify, as time related discussions can bring out a laundry >> list of issues, I would like to focus this discussion on providing a 2038 >> solution for existing interfaces and

Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder

2014-08-12 Thread josh
On Tue, Aug 12, 2014 at 05:08:53PM -0700, John Stultz wrote: > Also, just to clarify, as time related discussions can bring out a laundry > list of issues, I would like to focus this discussion on providing a 2038 > solution for existing interfaces and applications in a way that ideally > doesn't r