From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [put pull] timestamp stuff
Date: Tue, 4 Feb 2020 15:00:15 +0000 [thread overview]
Message-ID: <20200204150015.GR23230@ZenIV.linux.org.uk> (raw)
More 64bit timestamp work
The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git imm.timestamp
for you to fetch changes up to f0f3588f7a95bb8e02b0f8f5138efb7064665730:
kernfs: don't bother with timestamp truncation (2019-12-08 19:10:57 -0500)
----------------------------------------------------------------
Al Viro (1):
kernfs: don't bother with timestamp truncation
Amir Goldstein (1):
utimes: Clamp the timestamps in notify_change()
Deepa Dinamani (6):
fs: fat: Eliminate timespec64_trunc() usage
fs: cifs: Delete usage of timespec64_trunc
fs: ceph: Delete timespec64_trunc() usage
fs: ubifs: Eliminate timespec64_trunc() usage
fs: Delete timespec64_trunc()
fs: Do not overload update_time
fs/attr.c | 23 +++++++++++------------
fs/ceph/mds_client.c | 4 +---
fs/cifs/inode.c | 13 +++++++------
fs/configfs/inode.c | 9 +++------
fs/f2fs/file.c | 18 ++++++------------
fs/fat/misc.c | 10 +++++++++-
fs/inode.c | 33 +++------------------------------
fs/kernfs/inode.c | 6 +++---
fs/ntfs/inode.c | 18 ++++++------------
fs/ubifs/file.c | 18 ++++++------------
fs/ubifs/sb.c | 11 ++++-------
fs/utimes.c | 4 ++--
include/linux/fs.h | 1 -
13 files changed, 61 insertions(+), 107 deletions(-)
next reply other threads:[~2020-02-04 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:00 Al Viro [this message]
2020-02-05 6:53 ` [put pull] timestamp stuff Linus Torvalds
2020-02-05 16:08 ` Konstantin Ryabitsev
2020-02-05 16:25 ` Al Viro
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=20200204150015.GR23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).