From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>
Subject: [PATCH v2 0/7] regulator: core: locking cleanups, part 1/inf
Date: Wed, 30 Aug 2023 19:35:30 +0200 [thread overview]
Message-ID: <cover.1693416477.git.mirq-linux@rere.qmqm.pl> (raw)
This series aims to reduce regulator locking code complexity. There is
a consmetic fix (patch #6) included (applies to unexpected/unlikely
errors only). v2 adds a regulator_lock_contended() function to make the
ww_mutex locking sequence easier to understand.
Michał Mirosław (7):
regulator/core: regulator_lock_nested: remove `lock`
regulator/core: regulator_lock_nested: skip extra lock for -EDEADLK
regulator/core: regulator_lock_nested: simplify nested locking
regulator/core: regulator_resolve_supply: remove gotos
regulator/core: regulator_lock_contended: wrap ww_mutex lock sequence
restart
regulator/core: regulator_lock_two: propagate error up
regulator/core: regulator_lock_two: remove duplicate locking code
drivers/regulator/core.c | 133 +++++++++++++++++----------------------
1 file changed, 59 insertions(+), 74 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-30 18:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 17:35 Michał Mirosław [this message]
2023-08-30 17:35 ` [PATCH v2 1/7] regulator/core: regulator_lock_nested: remove `lock` Michał Mirosław
2023-08-30 17:35 ` [PATCH v2 2/7] regulator/core: regulator_lock_nested: skip extra lock for -EDEADLK Michał Mirosław
2023-08-30 17:35 ` [PATCH v2 3/7] regulator/core: regulator_lock_nested: simplify nested locking Michał Mirosław
2023-08-30 20:36 ` Stephen Boyd
2023-08-31 22:43 ` Michał Mirosław
2023-08-30 20:54 ` Doug Anderson
2023-08-31 22:41 ` Michał Mirosław
2023-08-30 17:35 ` [PATCH v2 5/7] regulator/core: regulator_lock_contended: wrap ww_mutex lock sequence restart Michał Mirosław
2023-08-30 20:21 ` Doug Anderson
2023-08-30 17:35 ` [PATCH v2 4/7] regulator/core: regulator_resolve_supply: remove gotos Michał Mirosław
2023-08-30 17:35 ` [PATCH v2 6/7] regulator/core: regulator_lock_two: propagate error up Michał Mirosław
2023-08-30 20:32 ` Doug Anderson
2023-08-30 17:35 ` [PATCH v2 7/7] regulator/core: regulator_lock_two: remove duplicate locking code Michał Mirosław
2023-08-30 20:33 ` Doug Anderson
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.1693416477.git.mirq-linux@rere.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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®