pwm: Use guards instead of explicity mutex_lock + mutex_unlock
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
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | pwm: Use guards for pwm_lock instead of explicity mutex_lock + mutex_unlockdrivers/ | +15 | 0 replies | |
| 2/3 | pwm: Use guards for export->lock instead of explicity mutex_lock + mutex_unlockdrivers/ | +8 | 0 replies | |
| 3/3 | pwm: Use guards for pwm_lookup_lock instead of explicity mutex_lock + mutex_unlockdrivers/ | +25 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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