summaryrefslogtreecommitdiff
path: root/%3fh%3dv4.5-rc4&id%3d32c6cdf75c9270848d2d0ed7c814eba05b47081f?h=v4.5-rc4&id=0...
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2018-01-28 12:17:35 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2018-01-28 12:17:35 -0800
commit07b0137c0268b8d0694a5f09284449353a1a6fed (patch)
treed69172d06f3553027ffa7be08e518697b2c58a9f /%3fh%3dv4.5-rc4&id%3d32c6cdf75c9270848d2d0ed7c814eba05b47081f?h=v4.5-rc4&id=07b0137c0268b8d0694a5f09284449353a1a6fed
parent624441927ff6af871d793dfa49fa347c8450e250 (diff)
parentd5421ea43d30701e03cadc56a38854c36a8b4433 (diff)
Merge branch 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fix from Thomas Gleixner: "A single fix for a ~10 years old problem which causes high resolution timers to stop after a CPU unplug/plug cycle due to a stale flag in the per CPU hrtimer base struct. Paul McKenney was hunting this for about a year, but the heisenbug nature made it resistant against debug attempts for quite some time" * 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: hrtimer: Reset hrtimer cpu base proper on CPU hotplug
Diffstat (limited to '%3fh%3dv4.5-rc4&id%3d32c6cdf75c9270848d2d0ed7c814eba05b47081f?h=v4.5-rc4&id=07b0137c0268b8d0694a5f09284449353a1a6fed')
0 files changed, 0 insertions, 0 deletions