From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/6] regulator: core: locking fixes and cleanups
Date: Sun, 20 Aug 2023 00:46:07 +0200 [thread overview]
Message-ID: <cover.1692484240.git.mirq-linux@rere.qmqm.pl> (raw)
This series reduces regulator locking code complexity. The single fix is
more a cosmetic one as it applies to unexpected (WARN-generating) error
paths.
Michał Mirosław (6):
regulator: core: simplify regulator_lock_nested()
regulator: core: skip nesting lock for -EDEADLK
regulator: core: simplify nested locking
regulator: core: remove `goto`s from resolve_supply()
regulator: core: propagate error out ouf regulator_lock_two()
regulator: core: simplify lock_two()
drivers/regulator/core.c | 110 +++++++++++++++------------------------
1 file changed, 42 insertions(+), 68 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-20 0:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 22:46 Michał Mirosław [this message]
2023-08-19 22:46 ` [PATCH 1/6] regulator: core: simplify regulator_lock_nested() Michał Mirosław
2023-08-21 16:50 ` Doug Anderson
2023-08-19 22:46 ` [PATCH 2/6] regulator: core: skip nesting lock for -EDEADLK Michał Mirosław
2023-08-21 16:50 ` Doug Anderson
2023-08-19 22:46 ` [PATCH 3/6] regulator: core: simplify nested locking Michał Mirosław
2023-08-21 16:50 ` Doug Anderson
2023-08-28 21:01 ` Michał Mirosław
2023-08-19 22:46 ` [PATCH 5/6] regulator: core: propagate error out ouf regulator_lock_two() Michał Mirosław
2023-08-21 16:50 ` Doug Anderson
2023-08-19 22:46 ` [PATCH 4/6] regulator: core: remove `goto`s from resolve_supply() Michał Mirosław
2023-08-21 16:50 ` Doug Anderson
2023-08-19 22:46 ` [PATCH 6/6] regulator: core: simplify lock_two() Michał Mirosław
2023-08-21 16:51 ` Doug Anderson
2023-08-28 20:26 ` Michał Mirosław
2023-08-29 20:52 ` Stephen Boyd
2023-08-29 21:25 ` Michał Mirosław
2023-08-29 22:57 ` Stephen Boyd
2023-08-30 17:25 ` Michał Mirosław
2023-08-30 18:53 ` Stephen Boyd
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=cover.1692484240.git.mirq-linux@rere.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=digetx@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®