summaryrefslogtreecommitdiffstats
path: root/fs/gfs2/glock.c
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2007-01-18 16:41:23 -0600
committerSteven Whitehouse <swhiteho@redhat.com>2007-02-05 13:37:38 -0500
commitddfe0627838ca0c0e8babb0dd2bd7f4b35e25bff (patch)
treea6348245a2a4d58705119a2cec5aabd650ee64a1 /fs/gfs2/glock.c
parent90101c31867b7acc44286b425d50e1042aa55b8d (diff)
downloadop-kernel-dev-ddfe0627838ca0c0e8babb0dd2bd7f4b35e25bff.zip
op-kernel-dev-ddfe0627838ca0c0e8babb0dd2bd7f4b35e25bff.tar.gz
[GFS2] use CURRENT_TIME_SEC instead of get_seconds in gfs2
I was looking something else up and came across this... I don't honestly have a good reason to change it other than to make it like every other Linux filesystem in this regard. ;-) It doesn't functionally change anything, but makes some lines shorter. :) I'm also curious; why does gfs2 have 64-bits of on-disk timestamps, but not in timespec_t format, and only stores second resolutions? Seems like you're halfway to sub-second resolutions already. I suppose if that gets implemented then all of the below should instead be CURRENT_TIME not CURRENT_TIME_SEC. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2/glock.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud