From: Richard Weinberger <richard@nod.at>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
y2038@lists.linaro.org, linux-fsdevel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Deepa Dinamani <deepa.kernel@gmail.com>, Jan Kara <jack@suse.cz>,
David Howells <dhowells@redhat.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: [PATCH 1/2] [RESEND] jffs2: use 64-bit intermediate timestamps
Date: Fri, 13 Jul 2018 22:47:13 +0200 [thread overview]
Message-ID: <2205649.NecG7tB80L@blindfold> (raw)
In-Reply-To: <20180713144739.3150217-1-arnd@arndb.de>
Am Freitag, 13. Juli 2018, 16:47:16 CEST schrieb Arnd Bergmann:
> The VFS now uses timespec64 timestamps consistently, but jffs2 still
> converts them to 32-bit numbers on the storage medium. As the helper
> functions for the conversion (get_seconds() and timespec_to_timespec64())
> are now deprecated, let's change them over to the more modern
> replacements.
>
> This keeps the traditional interpretation of those values, where
> the on-disk 32-bit numbers are taken to be negative numbers, i.e.
> dates before 1970, on 32-bit machines, but future numbers past 2038
> on 64-bit machines.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> I originally sent these two patches on Jun 19, but got no reply aside
> from a harmless sparse warning reported by the kbuild test robot.
>
> Looking at the git history for jffs2, it seems that David Woodhouse
> hasn't applied any patches for over two years, so I suppose he's
> not taking these either.
>
> Al or Andrew, could you pick these up instead?
We can carry it also via the MTD tree.
Thanks,
//richard
next prev parent reply other threads:[~2018-07-13 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:47 [PATCH 1/2] [RESEND] jffs2: use 64-bit intermediate timestamps Arnd Bergmann
2018-07-13 14:47 ` [PATCH 2/2] [RESEND] jffs2: use unsigned 32-bit timstamps consistently Arnd Bergmann
2018-07-13 20:47 ` Richard Weinberger [this message]
2018-07-17 19:54 ` [PATCH 1/2] [RESEND] jffs2: use 64-bit intermediate timestamps Boris Brezillon
2018-07-18 18:28 ` Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2205649.NecG7tB80L@blindfold \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=boris.brezillon@bootlin.com \
--cc=deepa.kernel@gmail.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).