Delete timespec64_trunc()
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | fs: fat: Eliminate timespec64_trunc() usagefs/ | +9 | 0 replies | |
| 2/6 | fs: cifs: Delete usage of timespec64_truncfs/ | +7 | 0 replies | |
| 3/6 | fs: ceph: Delete timespec64_trunc() usagefs/ | +1 | 3 replies | |
| 4/6 | fs: ubifs: Eliminate timespec64_trunc() usagefs/ | +4 | 0 replies | |
| 5/6 | fs: Delete timespec64_trunc()fs/ include/ | +0 | 0 replies | |
| 6/6 | fs: Do not overload update_timefs/ | +3 | 0 replies |
Reviews trailers per patch
1 of 6 patches has a Reviewed-by or Acked-by.
| Patch | Jeff Layton |
|---|---|
| 1/6 | |
| 2/6 | |
| 3/6 | A-b |
| 4/6 | |
| 5/6 | |
| 6/6 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/6] Delete timespec64_trunc()
This series aims at deleting timespec64_trunc(). There is a new api: timestamp_truncate() that is the replacement api. The api additionally does a limits check on the filesystem timestamps.
The suggestion to open code some of the truncate logic came from Al Viro. And, this does make the code in some filesystems easy to follow.
The series also does some update_time() cleanup as suggested by Al Viro.
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/ceph/mds_client.c | 4 +--- fs/cifs/inode.c | 13 +++++++------ fs/fat/misc.c | 10 +++++++++- fs/inode.c | 33 +++------------------------------ fs/ubifs/sb.c | 11 ++++------- include/linux/fs.h | 1 - 6 files changed, 24 insertions(+), 48 deletions(-)
Signature · 12 lines
Changes since v1: * Dropped the atime comparison (patch 2/7) taken through cifs tree. * Refactored update_time according to review comments. 2.17.1 Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected]