summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorManuel Ebner <manuelebnerli@mailbox.org>2026-09-04 14:20:04 +0200
committerUwe Kleine-König <ukleinek@kernel.org>2026-09-05 10:13:29 +0200
commit960909d2c63e0914bbf95d595dbc8e17babedd4b (patch)
tree088c5ef3905685318d04c780f5bde29701a1b54f
parent6b0c6ff76795f62981352cc0be00163077d0961b (diff)
downloadlinux-next-960909d2c63e0914bbf95d595dbc8e17babedd4b.tar.gz
linux-next-960909d2c63e0914bbf95d595dbc8e17babedd4b.zip
docs: pwm: Fix bracket and punctuation
Remove needless '(' and fix comma splice. Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org> Acked-by: Randy Dunlap <rdunlap@infradead.org> Link: https://patch.msgid.link/20260904122005.760299-2-manuelebnerli@mailbox.org Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
-rw-r--r--Documentation/driver-api/pwm.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/pwm.rst b/Documentation/driver-api/pwm.rst
index 0d27a40f5818..b6b67f7d4905 100644
--- a/Documentation/driver-api/pwm.rst
+++ b/Documentation/driver-api/pwm.rst
@@ -177,7 +177,7 @@ and pwm_put() may not be called from an atomic context.
Most functions in the PWM consumer API might sleep and so must not be called
from atomic context. The notable exception is pwm_apply_atomic() which has the
same semantics as pwm_apply_might_sleep() but can be called from atomic context.
-(The price for that is that it doesn't work for all PWM devices, use
+The price for that is that it doesn't work for all PWM devices. Use
pwm_might_sleep() to check if a given PWM supports atomic operation.
Locking in the PWM core ensures that callbacks related to a single chip are