On 2020-09-21 10:57:03 [+0100], Jonathan Cameron wrote: > So looking at this the other way, are there any significant risks associated > with this change? If not I'm tempted to queue them up and we have the rcX > time to fix anything we've missed (just like every other patch!) I've been told that it only performs IRQ-thread wake-ups in hard-IRQ context. This is fine then. Looking at the other series where ->try_renable() got renamed. It still looks like bmc150_accel_trig_try_reen() may acquire a mutex. Is it still the case or do I miss something essential? > Jonathan Sebastian
