Re: [PATCH 0/3] regulator: unexport regulator_lock/unlock()

2020-09-16 Thread Mark Brown
On Tue, Sep 15, 2020 at 08:55:06PM +0200, Michał Mirosław wrote: > On Mon, Sep 07, 2020 at 07:05:49PM +0100, Mark Brown wrote: > > [3/3] regulator: unexport regulator_lock/unlock() > > (no commit info) > It looks like the third one didn't get in? (Can't see it in the > for-next branch).

Re: [PATCH 0/3] regulator: unexport regulator_lock/unlock()

2020-09-15 Thread Michał Mirosław
On Mon, Sep 07, 2020 at 07:05:49PM +0100, Mark Brown wrote: > On Mon, 10 Aug 2020 06:33:30 +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

Re: [PATCH 0/3] regulator: unexport regulator_lock/unlock()

2020-09-05 Thread Michał Mirosław
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

[PATCH 0/3] regulator: unexport regulator_lock/unlock()

2020-08-09 Thread Michał Mirosław
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