On Wed, Mar 11, 2015 at 11:24:34AM +0800, Xunlei Pang wrote:
> From: Xunlei Pang
>
> As part of addressing "y2038 problem" for in-kernel uses, this
> patch adds the y2038-safe tegra_read_persistent_clock64() using
> timespec64.
>
> Because we rely on some subsequent changes to convert arm
On Wed, Mar 11, 2015 at 11:24:34AM +0800, Xunlei Pang wrote:
From: Xunlei Pang pang.xun...@linaro.org
As part of addressing y2038 problem for in-kernel uses, this
patch adds the y2038-safe tegra_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to
From: Xunlei Pang
As part of addressing "y2038 problem" for in-kernel uses, this
patch adds the y2038-safe tegra_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to convert arm multiarch
support, tegra_read_persistent_clock() will be removed then.
From: Xunlei Pang pang.xun...@linaro.org
As part of addressing y2038 problem for in-kernel uses, this
patch adds the y2038-safe tegra_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to convert arm multiarch
support, tegra_read_persistent_clock() will be
4 matches
Mail list logo