[PATCH] backlight: ktd253: fix comment typo

[PATCH] backlight: ktd253: fix comment typo

[Ruslan Vagner]

Fix the spelling in comments. No functional change.

Signed-off-by: Ruslan Vagner <rusya92266@gmail.com>
---
 drivers/video/backlight/ktd253-backlight.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/backlight/ktd253-backlight.c
b/drivers/video/backlight/ktd253-backlight.c
index 327b4ee75254..f2c5527d02e0 100644
--- a/drivers/video/backlight/ktd253-backlight.c
+++ b/drivers/video/backlight/ktd253-backlight.c
@@ -53,7 +53,7 @@ static int ktd253_backlight_stepdown(struct
ktd253_backlight *ktd253)
 	 *
 	 * Architectures do not always support ndelay() and we will get a few us
 	 * instead. If we get to a critical time limit an interrupt has likely
-	 * occured in the low part of the loop and we need to restart from the
+	 * occurred in the low part of the loop and we need to restart from the
 	 * top so we have the backlight in a known state.
 	 */
 	u64 ns;
-- 
2.54.0.windows.1

Re: [PATCH] backlight: ktd253: fix comment typo

[Lee Jones]

On Tue, 15 Sep 2026, Ruslan Vagner wrote:

> Fix the spelling in comments. No functional change.

Please expand on the subject line and the commit message.

What are you correcting helps?

This may sound pernickety, but it's important for some workflows that
subject lines are unique.  If someone fixes another typo in this file
and uses the same subject line, those workflows fail.

> Signed-off-by: Ruslan Vagner <rusya92266@gmail.com>
> ---
>  drivers/video/backlight/ktd253-backlight.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/video/backlight/ktd253-backlight.c
> b/drivers/video/backlight/ktd253-backlight.c
> index 327b4ee75254..f2c5527d02e0 100644
> --- a/drivers/video/backlight/ktd253-backlight.c
> +++ b/drivers/video/backlight/ktd253-backlight.c
> @@ -53,7 +53,7 @@ static int ktd253_backlight_stepdown(struct
> ktd253_backlight *ktd253)
>  	 *
>  	 * Architectures do not always support ndelay() and we will get a few us
>  	 * instead. If we get to a critical time limit an interrupt has likely
> -	 * occured in the low part of the loop and we need to restart from the
> +	 * occurred in the low part of the loop and we need to restart from the
>  	 * top so we have the backlight in a known state.
>  	 */
>  	u64 ns;
> -- 
> 2.54.0.windows.1

-- 
Lee Jones