redonkable/remarkable-linux
redonkable/remarkable-linux
1
0
Fork 0
Code Releases Activity

kernel/posix-cpu-timers.c: fix sparse warning

Browse source 
Sparse reports the following in kernel/posix-cpu-timers.c:

  warning: symbol 'firing' shadows an earlier one

Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
Cc: Subrata Modak <subrata@linux.vnet.ibm.com>
LKML-Reference: <BD79186B4FD85F4B8E60E381CAEE1909016C1AFE@mi8nycmail19.Mi8.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
H Hartley Sweeten 2009-04-29 19:14:32 -04:00 committed by Ingo Molnar
parent 314eeac9e3
commit 6e85c5ba73
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
kernel/posix-cpu-timers.c
View file

@ -1420,19 +1420,19 @@ void run_posix_cpu_timers(struct task_struct *tsk)
* timer call will interfere. * timer call will interfere.
*/ */
list_for_each_entry_safe(timer, next, &firing, it.cpu.entry) { list_for_each_entry_safe(timer, next, &firing, it.cpu.entry) {
int firing; int cpu_firing;
spin_lock(&timer->it_lock); spin_lock(&timer->it_lock);
list_del_init(&timer->it.cpu.entry); list_del_init(&timer->it.cpu.entry);
firing = timer->it.cpu.firing; cpu_firing = timer->it.cpu.firing;
timer->it.cpu.firing = 0; timer->it.cpu.firing = 0;
/* /*
* The firing flag is -1 if we collided with a reset * The firing flag is -1 if we collided with a reset
* of the timer, which already reported this * of the timer, which already reported this
* almost-firing as an overrun. So don't generate an event. * almost-firing as an overrun. So don't generate an event.
*/ */
if (likely(firing >= 0)) { if (likely(cpu_firing >= 0))
cpu_timer_fire(timer); cpu_timer_fire(timer);
}
spin_unlock(&timer->it_lock); spin_unlock(&timer->it_lock);
} }
} }