[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1401695682.11182.108.camel@sauron.fi.intel.com>
Date: Mon, 02 Jun 2014 10:54:42 +0300
From: Artem Bityutskiy <dedekind1@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
joseph@...esourcery.com, john.stultz@...aro.org, hch@...radead.org,
tglx@...utronix.de, geert@...ux-m68k.org, lftan@...era.com,
hpa@...or.com, linux-fsdevel@...r.kernel.org,
Adrian Hunter <adrian.hunter@...el.com>,
linux-mtd@...ts.infradead.org
Subject: Re: [RFC 17/32] ubifs: convert to struct inode_time
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 <arnd@...db.de>
> Cc: Artem Bityutskiy <dedekind1@...il.com>
> Cc: Adrian Hunter <adrian.hunter@...el.com>
> Cc: linux-mtd@...ts.infradead.org
Looks fine from UBIFS POW, thanks!
--
Best Regards,
Artem Bityutskiy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists