Skip to content

pwm: Use guards instead of explicity mutex_lock + mutex_unlock

Uwe Kleine-König linux-pwm 1 version Applied

Status from this message: I applied the series to my pwm/for-next branch.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 1 replyApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3pwm: Use guards for pwm_lock instead of explicity mutex_lock + mutex_unlockdrivers/pwm/core.c+15 -370 replies
2/3pwm: Use guards for export->lock instead of explicity mutex_lock + mutex_unlockdrivers/pwm/core.c+8 -110 replies
3/3pwm: Use guards for pwm_lookup_lock instead of explicity mutex_lock + mutex_unlockdrivers/pwm/core.c+25 -320 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] pwm: Use guards instead of explicity mutex_lock + mutex_unlock

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

Signature · 1 line
2.43.0