Commit-ID: 13e792a19d4e3a1c64e94197ba357685fd584ded Gitweb: https://git.kernel.org/tip/13e792a19d4e3a1c64e94197ba357685fd584ded Author: Laurent Gauthier <laurent.gauthier@xxxxxxxxxxxx> AuthorDate: Sat, 5 Jan 2019 00:07:45 +0100 Committer: Ingo Molnar <mingo@xxxxxxxxxx> CommitDate: Fri, 19 Apr 2019 19:17:04 +0200 tick: Fix typos in comments Signed-off-by: Laurent Gauthier <laurent.gauthier@xxxxxxxxxxxx> Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx> Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx> Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx> --- kernel/time/tick-broadcast.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c index 7541cbca695e..e51778c312f1 100644 --- a/kernel/time/tick-broadcast.c +++ b/kernel/time/tick-broadcast.c @@ -809,13 +809,13 @@ int __tick_broadcast_oneshot_control(enum tick_broadcast_state state) * either the CPU handling the broadcast * interrupt or we got woken by something else. * - * We are not longer in the broadcast mask, so + * We are no longer in the broadcast mask, so * if the cpu local expiry time is already * reached, we would reprogram the cpu local * timer with an already expired event. * * This can lead to a ping-pong when we return - * to idle and therefor rearm the broadcast + * to idle and therefore rearm the broadcast * timer before the cpu local timer was able * to fire. This happens because the forced * reprogramming makes sure that the event
![]() |