On Mon, Aug 10, 2020 at 06:33:30AM +0200, Michał Mirosław wrote: > This removes regulator_lock/unlock() calls around > regulator_notifier_call_chain() as they are redundant - drivers > already have to guarantee regulator_dev's existence during the call. > > This should make reasoing about the lock easier, as this was the only > use outside regulator core code. > > The only client that needed recursive locking from the notifier chain > was drivers/usb/host/ohci-da8xx.c, which responds to over-current > notification by calling regulator_disable().
I can't see the series in regulator/for-next and got no comments. Should I resend? As a side note: this is a step towards fixing regulator-coupling-related locking issues. Best Regards, Michał Mirosław
