On Mon, 2016-11-07 at 19:16 +0000, Will Deacon wrote: > On Mon, Nov 07, 2016 at 02:12:13PM -0500, Rik van Riel wrote: > > > > On Mon, 2016-11-07 at 19:36 +0100, Thomas Gleixner wrote: > > > > > > On Mon, 7 Nov 2016, Thomas Gleixner wrote: > > > > > > > > > > > > > > > > > > > > > > > == Missing oneshot_stopped callbacks == > > > > > > > > > > I raised the issue that various clock_event_device sources > > > > > don't > > > > > always support oneshot_stopped, which can cause an additional > > > > > final interrupt to occur after the timer infrastructure > > > > > believes > > > > > the > > > > > interrupt has been stopped. I have patches to fix this for > > > > > tile > > > > > and > > > > > arm64 in my patch series; Thomas volunteered to look at > > > > > adding > > > > > equivalent support for x86. > > > > > > > > Right. > > > > > > Untested patch below should fix that. > > > > > > > That whitespace cleanup looks awesome, but I am not > > optimistic about its chances to bring about functional > > change. > > > > What am I overlooking? > > It hooks up .set_state_oneshot_stopped?
Gah, indeed. Never mind :) -- All Rights Reversed.
signature.asc
Description: This is a digitally signed message part
