diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-04-17 19:53:01 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-04-17 19:53:01 +0300 |
| commit | fbb9c58e56f2ee56e77b19fdfac131d57d3341c1 (patch) | |
| tree | ed4634eba7260571f38abad8007e70198b215000 /tools | |
| parent | 0e59732ed61a24458b6875c162660dc0758b678f (diff) | |
| parent | 9c95bc25ad3b1a2240cd1f896569292a57d3ce85 (diff) | |
| download | linux-fbb9c58e56f2ee56e77b19fdfac131d57d3341c1.tar.xz | |
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')
0 files changed, 0 insertions, 0 deletions