Re: [PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-09 Thread Deepa Dinamani
On Thu, Jun 9, 2016 at 12:41 AM, Jan Kara wrote: > On Wed 08-06-16 22:04:50, Deepa Dinamani wrote: >> Logical Volume Integrity format is described to have the >> same timestamp format for "Recording Date and time" as >> the other [a,c,m]timestamps. >> Hence using current_fs_time()

Re: [PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-09 Thread Deepa Dinamani
On Thu, Jun 9, 2016 at 12:41 AM, Jan Kara wrote: > On Wed 08-06-16 22:04:50, Deepa Dinamani wrote: >> Logical Volume Integrity format is described to have the >> same timestamp format for "Recording Date and time" as >> the other [a,c,m]timestamps. >> Hence using current_fs_time() instead here

Re: [PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-09 Thread Jan Kara
On Wed 08-06-16 22:04:50, Deepa Dinamani wrote: > CURRENT_TIME is not y2038 safe. > > CURRENT_TIME macro is also not appropriate for filesystems > as it doesn't use the right granularity for filesystem > timestamps. > > Logical Volume Integrity format is described to have the > same timestamp

Re: [PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-09 Thread Jan Kara
On Wed 08-06-16 22:04:50, Deepa Dinamani wrote: > CURRENT_TIME is not y2038 safe. > > CURRENT_TIME macro is also not appropriate for filesystems > as it doesn't use the right granularity for filesystem > timestamps. > > Logical Volume Integrity format is described to have the > same timestamp

[PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-08 Thread Deepa Dinamani
CURRENT_TIME is not y2038 safe. CURRENT_TIME macro is also not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Logical Volume Integrity format is described to have the same timestamp format for "Recording Date and time" as the other

[PATCH 06/21] fs: udf: Replace CURRENT_TIME with current_fs_time()

2016-06-08 Thread Deepa Dinamani
CURRENT_TIME is not y2038 safe. CURRENT_TIME macro is also not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Logical Volume Integrity format is described to have the same timestamp format for "Recording Date and time" as the other