From: "Michał Mirosław" <firstname.lastname@example.org> To: Liam Girdwood <email@example.com>, Mark Brown <firstname.lastname@example.org>, Dmitry Osipenko <email@example.com> Cc: firstname.lastname@example.org, email@example.com Subject: Re: [PATCH 0/3] regulator: unexport regulator_lock/unlock() Date: Sun, 6 Sep 2020 02:07:17 +0200 [thread overview] Message-ID: <20200906000717.GA3731@qmqm.qmqm.pl> (raw) In-Reply-To: <firstname.lastname@example.org> 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
next prev parent reply other threads:[~2020-09-06 0:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-10 4:33 Michał Mirosław 2020-08-10 4:33 ` [PATCH 2/3] regulator: remove locking around regulator_notifier_call_chain() Michał Mirosław 2020-08-10 14:17 ` Adam Thomson 2020-09-06 11:58 ` Dmitry Osipenko 2020-08-10 4:33 ` [PATCH 1/3] regulator: don't require mutex for regulator_notifier_call_chain() Michał Mirosław 2020-09-06 11:55 ` Dmitry Osipenko 2020-08-10 4:33 ` [PATCH 3/3] regulator: unexport regulator_lock/unlock() Michał Mirosław 2020-09-06 11:59 ` Dmitry Osipenko 2020-09-06 0:07 ` Michał Mirosław [this message] [not found] ` <email@example.com> 2020-09-15 18:55 ` [PATCH 0/3] " Michał Mirosław 2020-09-16 10:36 ` Mark Brown 2020-09-19 21:28 ` [PATCH v2] " Michał Mirosław
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200906000717.GA3731@qmqm.qmqm.pl \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/3] regulator: unexport regulator_lock/unlock()' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).