From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 04/25] avr32: Add 32 bit time_t and clock_t Date: Wed, 14 May 2014 14:39:18 -0700 Message-ID: <5373E286.2080104@zytor.com> References: <1399971456-3941-1-git-send-email-lftan@altera.com> <1399971769-4116-1-git-send-email-lftan@altera.com> <20140513201944.GA14023@samfundet.no> <20140514074456.GB17409@samfundet.no> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:60900 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752738AbaENVji (ORCPT ); Wed, 14 May 2014 17:39:38 -0400 In-Reply-To: <20140514074456.GB17409@samfundet.no> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Hans-Christian Egtvedt , Ley Foon Tan Cc: Linux-Arch , "linux-kernel@vger.kernel.org" , Chung-Lin Tang , Haavard Skinnemoen On 05/14/2014 12:44 AM, Hans-Christian Egtvedt wrote: >> In this patchset, the generic one will be 64 bit (long long). So, the >> existing 32 bit users need to override this. > > Would it be wrong to use the architecture defined size, or does some 32-bit > architectures use 64-bit time types? This is what we had done up until now, except for x32, *AND THAT IS EXACTLY THE PROBLEM*. 2038 is only 24 years away. -hpa