Documentation/driver-api/pwm.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Remove needless '(' and fix comma splice.
Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
CC: Randy Dunlap <rdunlap@infradead.org>
---
[v2]
fix comma splice as Randy suggested.
[v1]
https://lore.kernel.org/all/20260903160535.734369-2-manuelebnerli@mailbox.org/
---
Documentation/driver-api/pwm.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-api/pwm.rst b/Documentation/driver-api/pwm.rst
index 0d27a40f5..b6b67f7d4 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
--
2.54.0
Hello,
On Fri, Sep 04, 2026 at 02:20:04PM +0200, Manuel Ebner wrote:
> Remove needless '(' and fix comma splice.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> CC: Randy Dunlap <rdunlap@infradead.org>
applied with Randy's Ack to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
as 7.4-rc1 material.
Best regards
Uwe
On 9/4/26 5:20 AM, Manuel Ebner wrote:
> Remove needless '(' and fix comma splice.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> CC: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> [v2]
> fix comma splice as Randy suggested.
>
> [v1]
> https://lore.kernel.org/all/20260903160535.734369-2-manuelebnerli@mailbox.org/
> ---
> Documentation/driver-api/pwm.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/pwm.rst b/Documentation/driver-api/pwm.rst
> index 0d27a40f5..b6b67f7d4 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
--
~Randy
© 2016 - 2026 Red Hat, Inc.