[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a1bfy0xDninx0Er-L-2bbEh5-5ZOE6g2ZAVa-UcLNZMAA@mail.gmail.com>
Date: Fri, 13 Jul 2018 16:30:01 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Richard Weinberger <richard@....at>
Cc: Artem Bityutskiy <dedekind1@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Eric Biggers <ebiggers@...gle.com>, Jan Kara <jack@...e.cz>,
Deepa Dinamani <deepa.kernel@...il.com>,
Souptick Joarder <jrdr.linux@...il.com>,
Jérôme Glisse <jglisse@...hat.com>,
Hyunchul Lee <cheol.lee@....com>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ubifs: use timespec64 for inode timestamps
On Mon, Jul 2, 2018 at 4:20 PM, Richard Weinberger <richard@....at> wrote:
> Am Mittwoch, 20. Juni 2018, 10:12:58 CEST schrieb Arnd Bergmann:
>> Both vfs and the on-disk inode structures can deal with fine-grained
>> timestamps now, so this is the last missing piece to make ubifs
>> y2038-safe on 32-bit architectures.
>
> Acked-by: Richard Weinberger <richard@....at>
>
> Shall this patch go through the ubifs tree?
Sorry I missed the question earlier. Yes, it would be nice if you could pick
it up there. I'm resending both patches now for your convenience.
Arnd
Powered by blists - more mailing lists