[PATCH 16/38] tick-common: don't pass cpumask to tick_setup_device()

[Viresh Kumar]

tick_setup_device() is always passed cpumask of 'cpu', which is also passed as
parameter to this routine. So, just calculate the cpumask(cpu) in
tick_setup_device() instead of passing from every caller.

Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
---
 kernel/time/tick-common.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c
index c1b3619..c2aa441 100644
--- a/kernel/time/tick-common.c
+++ b/kernel/time/tick-common.c
@@ -145,9 +145,9 @@ void tick_setup_periodic(struct clock_event_device *dev, 
int broadcast)
  * Setup the tick device
  */
 static void tick_setup_device(struct tick_device *td,
-                             struct clock_event_device *newdev, int cpu,
-                             const struct cpumask *cpumask)
+                             struct clock_event_device *newdev, int cpu)
 {
+       const struct cpumask *cpumask = cpumask_of(cpu);
        ktime_t next_event;
        void (*handler)(struct clock_event_device *) = NULL;
 
@@ -209,7 +209,7 @@ void tick_install_replacement(struct clock_event_device 
*newdev)
        int cpu = smp_processor_id();
 
        clockevents_exchange_device(td->evtdev, newdev);
-       tick_setup_device(td, newdev, cpu, cpumask_of(cpu));
+       tick_setup_device(td, newdev, cpu);
        if (newdev->features & CLOCK_EVT_FEAT_ONESHOT)
                tick_oneshot_notify();
 }
@@ -293,7 +293,7 @@ void tick_check_new_device(struct clock_event_device 
*newdev)
                curdev = NULL;
        }
        clockevents_exchange_device(curdev, newdev);
-       tick_setup_device(td, newdev, cpu, cpumask_of(cpu));
+       tick_setup_device(td, newdev, cpu);
        if (newdev->features & CLOCK_EVT_FEAT_ONESHOT)
                tick_oneshot_notify();
        return;
-- 
1.7.12.rc2.18.g61b472e

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/