Re: [PATCH 1/8] time: Add y2038 safe read_boot_clock64()

On Wed, Mar 18, 2015 at 5:48 AM, wrote: > Ping ... Thanks for the reminder. Since there's not been any objections, I'm queuing this up. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH 1/8] time: Add y2038 safe read_boot_clock64()

On Wed, Mar 18, 2015 at 5:48 AM, pang.xun...@zte.com.cn wrote: Ping ... Thanks for the reminder. Since there's not been any objections, I'm queuing this up. thanks -john -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to

[PATCH 1/8] time: Add y2038 safe read_boot_clock64()

From: Xunlei Pang As part of addressing in-kernel y2038 issues, this patch adds read_boot_clock64() and replaces all the call sites of read_boot_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe read_boot_clock(). This allows architecture

[PATCH 1/8] time: Add y2038 safe read_boot_clock64()

From: Xunlei Pang pang.xun...@linaro.org As part of addressing in-kernel y2038 issues, this patch adds read_boot_clock64() and replaces all the call sites of read_boot_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe read_boot_clock().