]> err.no Git - linux-2.6/commit
[GFS2] use CURRENT_TIME_SEC instead of get_seconds in gfs2
authorEric Sandeen <sandeen@redhat.com>
Thu, 18 Jan 2007 22:41:23 +0000 (16:41 -0600)
committerSteven Whitehouse <swhiteho@redhat.com>
Mon, 5 Feb 2007 18:37:38 +0000 (13:37 -0500)
commitddfe0627838ca0c0e8babb0dd2bd7f4b35e25bff
treea6348245a2a4d58705119a2cec5aabd650ee64a1
parent90101c31867b7acc44286b425d50e1042aa55b8d
[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>
fs/gfs2/bmap.c
fs/gfs2/dir.c
fs/gfs2/inode.c
fs/gfs2/ops_inode.c