diff options
| author | Johannes Berg <johannes.berg@intel.com> | 2021-01-15 14:49:45 +0300 |
|---|---|---|
| committer | Richard Weinberger <richard@nod.at> | 2021-01-27 00:11:38 +0300 |
| commit | 7f3414226b58b0df0426104c8ab5e8d50ae71d11 (patch) | |
| tree | b98f6a25b6157c873cb66a71729bd82f223d7daf /arch/arm/boot/dts/ste-snowball.dts | |
| parent | 9868c2081d071f7c309796c8dffc94364fc07582 (diff) | |
| download | linux-7f3414226b58b0df0426104c8ab5e8d50ae71d11.tar.xz | |
um: time: fix initialization in time-travel mode
In time-travel mode, since my previous patch, the start time was
initialized too late, so that the system would read it before we
set it, thus always starting system time at 0 (1970-01-01). This
happens because timekeeping_init() reads the time and is called
before time_init().
Unfortunately, I didn't see this before because I was testing it
only with the RTC patch applied (and enabled), and then the time
is read again by the RTC a little - after time_init() this time.
Fix this by just doing the initialization whenever necessary.
Fixes: 2701c1bd91dd ("um: time: Fix read_persistent_clock64() in time-travel")
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'arch/arm/boot/dts/ste-snowball.dts')
0 files changed, 0 insertions, 0 deletions