[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <537699E7.9050005@zytor.com>
Date: Fri, 16 May 2014 16:06:15 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Christoph Hellwig <hch@...radead.org>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
CC: Arnd Bergmann <arnd@...db.de>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ley Foon Tan <lftan@...era.com>,
Linux-Arch <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
LeyFoon Tan <lftan.linux@...il.com>,
Chung-Lin Tang <cltang@...esourcery.com>
Subject: Re: [PATCH 00/25] Change time_t and clock_t to 64 bit
On 05/16/2014 12:48 AM, Christoph Hellwig wrote:
>
> The stat(64) syscall already has stopped time_t for a long time:
>
> struct stat64 {
> ...
> int st_atime; /* Time of last access. */
> unsigned int st_atime_nsec;
> int st_mtime; /* Time of last modification. */
> unsigned int st_mtime_nsec;
> int st_ctime; /* Time of last status change. */
> unsigned int st_ctime_nsec;
> };
>
... except that that is really a struct timespec just written weirdly,
and userspace uses it as a struct timespec.
-hpa
--
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