diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-01-27 16:37:40 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-01-27 16:37:40 -0800 |
| commit | a56c41e5d766871231828046f477611d6ee7d2db (patch) | |
| tree | 411226578e61acba6ddcdd7d440eb225f6ed1a71 /arch/arm/mach-mmp/clock-pxa910.c | |
| parent | b1dba2473114588be3df916bf629a61bdcc83737 (diff) | |
| parent | 9f24c540f7f8eb3a981528da9a9a636a5bdf5987 (diff) | |
| download | linux-a56c41e5d766871231828046f477611d6ee7d2db.tar.bz2 | |
Merge tag 'timers-urgent-2020-01-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fixes from Thomas Gleixner:
"Two fixes for the generic VDSO code which missed 5.5:
- Make the update to the coarse timekeeper unconditional.
This is required because the coarse timekeeper interfaces in the
VDSO do not depend on a VDSO capable clocksource. If the system
does not have a VDSO capable clocksource and the update is
depending on the VDSO capable clocksource, the coarse VDSO
interfaces would operate on stale data forever.
- Invert the logic of __arch_update_vdso_data() to avoid further head
scratching.
Tripped over this several times while analyzing the update problem
above"
* tag 'timers-urgent-2020-01-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
lib/vdso: Update coarse timekeeper unconditionally
lib/vdso: Make __arch_update_vdso_data() logic understandable
Diffstat (limited to 'arch/arm/mach-mmp/clock-pxa910.c')
0 files changed, 0 insertions, 0 deletions