On Mon, Oct 28, 2019 at 08:21:08AM -0700, Davidlohr Bueso wrote: > On Mon, 28 Oct 2019, Stefan Wahren wrote: > > > Hi Davidlohr, > > > > Am 27.10.19 um 23:15 schrieb Davidlohr Bueso: > > > There seems no need to be using a semaphore, or a sleeping lock > > > in the first place: critical region is extremely short, does not > > > call into any blocking calls and furthermore lock and unlocking > > > operations occur in the same context. > > > > > > Get rid of another semaphore user by replacing it with a spinlock. > > > > > > Signed-off-by: Davidlohr Bueso <dave@xxxxxxxxxxxx> > > > --- > > > This is in an effort to further reduce semaphore users in the kernel. > > > > > thanks for this. Could please also send this to devel@xxxxxxxxxxxxxxxxxxxx? > > Ccing. I don't see a patch here :( _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
