Sean Hefty wrote: > I think we should just remove cma_disable_remove() and cma_enable_remove(), and instead call mutex_lock/unlock directly in their places. Where cma_disable_remove() is called, add in appropriate state checks after acquiring > the mutex. OK, will do that. Or.