Commit-ID: ffa48c0d76803057ee89bf220305466d74256d7b Gitweb: http://git.kernel.org/tip/ffa48c0d76803057ee89bf220305466d74256d7b Author: Rafael J. Wysocki <rafael.j.wyso...@intel.com> AuthorDate: Fri, 3 Apr 2015 02:36:10 +0200 Committer: Ingo Molnar <mi...@kernel.org> CommitDate: Fri, 3 Apr 2015 08:44:36 +0200
clockevents: Remove broadcast oneshot control leftovers Now that all users are converted over to explicit calls into the clockevents state machine, remove the notification chain leftovers. Original-from: Thomas Gleixner <t...@linutronix.de> Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com> Cc: Peter Zijlstra <pet...@infradead.org> Cc: Linus Torvalds <torva...@linux-foundation.org> Cc: Andrew Morton <a...@linux-foundation.org> Cc: John Stultz <john.stu...@linaro.org> Link: http://lkml.kernel.org/r/14018863.nquzkfu...@vostro.rjw.lan Signed-off-by: Ingo Molnar <mi...@kernel.org> --- include/linux/clockchips.h | 2 -- kernel/time/clockevents.c | 7 ------- 2 files changed, 9 deletions(-) diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h index 438fafa..f97f498 100644 --- a/include/linux/clockchips.h +++ b/include/linux/clockchips.h @@ -11,8 +11,6 @@ /* Clock event notification values */ enum clock_event_nofitiers { CLOCK_EVT_NOTIFY_ADD, - CLOCK_EVT_NOTIFY_BROADCAST_ENTER, - CLOCK_EVT_NOTIFY_BROADCAST_EXIT, CLOCK_EVT_NOTIFY_CPU_DYING, CLOCK_EVT_NOTIFY_CPU_DEAD, }; diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c index 7791b1c..be9abf3 100644 --- a/kernel/time/clockevents.c +++ b/kernel/time/clockevents.c @@ -655,13 +655,6 @@ int clockevents_notify(unsigned long reason, void *arg) raw_spin_lock_irqsave(&clockevents_lock, flags); switch (reason) { - case CLOCK_EVT_NOTIFY_BROADCAST_ENTER: - tick_broadcast_enter(); - break; - case CLOCK_EVT_NOTIFY_BROADCAST_EXIT: - tick_broadcast_exit(); - break; - case CLOCK_EVT_NOTIFY_CPU_DYING: tick_handover_do_timer(arg); break; -- 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/
