summaryrefslogtreecommitdiffstats
path: root/tools/arch
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-04-17 18:53:01 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2022-04-17 18:53:01 +0200
commitfbb9c58e56f2ee56e77b19fdfac131d57d3341c1 (patch)
treeed4634eba7260571f38abad8007e70198b215000 /tools/arch
parentMerge tag 'smp-urgent-2022-04-17' of git://git.kernel.org/pub/scm/linux/kerne... (diff)
parenttick/sched: Fix non-kernel-doc comment (diff)
downloadlinux-fbb9c58e56f2ee56e77b19fdfac131d57d3341c1.tar.xz
linux-fbb9c58e56f2ee56e77b19fdfac131d57d3341c1.zip
Merge tag 'timers-urgent-2022-04-17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fixes from Thomas Gleixner: "A small set of fixes for the timers core: - Fix the warning condition in __run_timers() which does not take into account that a CPU base (especially the deferrable base) never has a timer armed on it and therefore the next_expiry value can become stale. - Replace a WARN_ON() in the NOHZ code with a WARN_ON_ONCE() to prevent endless spam in dmesg. - Remove the double star from a comment which is not meant to be in kernel-doc format" * tag 'timers-urgent-2022-04-17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: tick/sched: Fix non-kernel-doc comment tick/nohz: Use WARN_ON_ONCE() to prevent console saturation timers: Fix warning condition in __run_timers()
Diffstat (limited to 'tools/arch')
0 files changed, 0 insertions, 0 deletions