From mboxrd@z Thu Jan 1 00:00:00 1970 From: Artem Bityutskiy Subject: Re: [RFC 17/32] ubifs: convert to struct inode_time Date: Mon, 02 Jun 2014 10:54:42 +0300 Message-ID: <1401695682.11182.108.camel@sauron.fi.intel.com> References: <1401480116-1973111-1-git-send-email-arnd@arndb.de> <1401480116-1973111-18-git-send-email-arnd@arndb.de> Reply-To: dedekind1@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com ([192.55.52.93]:65082 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751796AbaFBHys (ORCPT ); Mon, 2 Jun 2014 03:54:48 -0400 In-Reply-To: <1401480116-1973111-18-git-send-email-arnd@arndb.de> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Arnd Bergmann Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, joseph@codesourcery.com, john.stultz@linaro.org, hch@infradead.org, tglx@linutronix.de, geert@linux-m68k.org, lftan@altera.com, hpa@zytor.com, linux-fsdevel@vger.kernel.org, Adrian Hunter , linux-mtd@lists.infradead.org On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote: > ubifs uses 64-bit integers for inode timestamps, which will work > practicall forever, but the VFS uses struct timespec for timestamps, > which is only good until 2038 on 32-bit CPUs. > > This gets us one small step closer to lifting the VFS limit by using > struct inode_time in ubifs. > > Signed-off-by: Arnd Bergmann > Cc: Artem Bityutskiy > Cc: Adrian Hunter > Cc: linux-mtd@lists.infradead.org Looks fine from UBIFS POW, thanks! -- Best Regards, Artem Bityutskiy