Re: [PATCH 20/35] clockevents: Provide explicit broadcast oneshot control function

* Peter Zijlstra [150216 05:13]: > From: Thomas Gleixner > > clockevents_notify() is a leftover from the early design of the > clockevents facility. It's really not a notification mechanism, it's a > multiplex call. We are way better off to have explicit calls instead of this > monstrosity. >

Re: [PATCH 20/35] clockevents: Provide explicit broadcast oneshot control function

* Peter Zijlstra pet...@infradead.org [150216 05:13]: From: Thomas Gleixner t...@linutronix.de clockevents_notify() is a leftover from the early design of the clockevents facility. It's really not a notification mechanism, it's a multiplex call. We are way better off to have explicit calls

[PATCH 20/35] clockevents: Provide explicit broadcast oneshot control function

From: Thomas Gleixner clockevents_notify() is a leftover from the early design of the clockevents facility. It's really not a notification mechanism, it's a multiplex call. We are way better off to have explicit calls instead of this monstrosity. Split out the broadcast oneshot control into a

[PATCH 20/35] clockevents: Provide explicit broadcast oneshot control function

From: Thomas Gleixner t...@linutronix.de clockevents_notify() is a leftover from the early design of the clockevents facility. It's really not a notification mechanism, it's a multiplex call. We are way better off to have explicit calls instead of this monstrosity. Split out the broadcast