From: Arnd Bergmann <arnd@arndb.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, y2038@lists.linaro.org,
tglx@linutronix.de, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 2/2] vfs: Add vfs_time accessors
Date: Sat, 9 Apr 2016 03:17:19 +0200 [thread overview]
Message-ID: <201604090317.19296.arnd@arndb.de> (raw)
In-Reply-To: <1460130431-7865-3-git-send-email-deepa.kernel@gmail.com>
On Friday 08 April 2016, Deepa Dinamani wrote:
> Add vfs_time accessors to help convert vfs timestamps to use
> 64 bit times. These create an abstraction layer so that
> vfs inode times can be switched to use struct timespec64 from
> struct timespec without breaking the individual filesystems
> after they have incorporated these.
>
> Use uapi exposed data types, timespec and timespec64 here to keep
> minimal timestamp data type conversions in API's interfacing with
> vfs.
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2016-04-09 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:47 [PATCH 0/2] Add infrastructure to support vfs 64 bit timestamps Deepa Dinamani
2016-04-08 15:47 ` [PATCH 1/2] fs: Add current_fs_time_sec() function Deepa Dinamani
2016-04-09 1:16 ` Arnd Bergmann
2016-04-08 15:47 ` [PATCH 2/2] vfs: Add vfs_time accessors Deepa Dinamani
2016-04-09 1:17 ` Arnd Bergmann [this message]
2016-04-08 15:49 ` [PATCH 0/2] Add infrastructure to support vfs 64 bit timestamps Thomas Gleixner
2016-04-17 22:39 ` [Y2038] " Arnd Bergmann
2016-04-26 16:15 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2016-03-02 15:31 [PATCH 0/2] Add infrastructure to support vfs 64 bit times Deepa Dinamani
2016-03-02 15:31 ` [PATCH 2/2] vfs: Add vfs_time accessors Deepa Dinamani
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=201604090317.19296.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.