Johannes Berg 7f3414226b 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: 2701c1bd91 ("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>		2021-01-26 22:11:38 +01:00
..
configs	um: Cleanup CONFIG_IOSCHED_CFQ	2020-03-29 23:15:22 +02:00
drivers	Revert "um: allocate a guard page to helper threads"	2021-01-26 22:11:38 +01:00
include	Revert "um: support some of ARCH_HAS_SET_MEMORY"	2021-01-26 22:11:38 +01:00
kernel	um: time: fix initialization in time-travel mode	2021-01-26 22:11:38 +01:00
os-Linux	um: fix os_idle_sleep() to not hang	2021-01-26 22:11:38 +01:00
scripts	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
.gitignore	.gitignore: add SPDX License Identifier	2020-03-25 11:50:48 +01:00
Kconfig	Revert "um: support some of ARCH_HAS_SET_MEMORY"	2021-01-26 22:11:38 +01:00
Kconfig.debug	treewide: replace '---help---' in Kconfig files with 'help'	2020-06-14 01:57:21 +09:00
Makefile	kbuild: remove cc-option test of -fno-stack-protector	2020-07-07 11:13:10 +09:00
Makefile-os-Linux
Makefile-skas