From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: linux-pwm@vger.kernel.org
Subject: [PATCH 0/3] pwm: Use guards instead of explicity mutex_lock + mutex_unlock
Date: Thu, 27 Jun 2024 22:31:18 +0200 [thread overview]
Message-ID: <cover.1719520143.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
I consider this a nice cleanup. It makes the code more compact and it's less
prone to error, because you cannot forget an unlock in an error path.
Best regards
Uwe
Uwe Kleine-König (3):
pwm: Use guards for pwm_lock instead of explicity mutex_lock + mutex_unlock
pwm: Use guards for export->lock instead of explicity mutex_lock + mutex_unlock
pwm: Use guards for pwm_lookup_lock instead of explicity mutex_lock + mutex_unlock
drivers/pwm/core.c | 128 +++++++++++++++++----------------------------
1 file changed, 48 insertions(+), 80 deletions(-)
base-commit: 888564d8d708d1c91900ed3a11761f46297fd748
--
2.43.0
next reply other threads:[~2024-06-27 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 20:31 Uwe Kleine-König [this message]
2024-06-27 20:31 ` [PATCH 1/3] pwm: Use guards for pwm_lock instead of explicity mutex_lock + mutex_unlock Uwe Kleine-König
2024-06-27 20:31 ` [PATCH 2/3] pwm: Use guards for export->lock " Uwe Kleine-König
2024-06-27 20:31 ` [PATCH 3/3] pwm: Use guards for pwm_lookup_lock " Uwe Kleine-König
2024-07-05 10:24 ` [PATCH 0/3] pwm: Use guards " Uwe Kleine-König
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.1719520143.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=linux-pwm@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