All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Ruslan Vagner <rusya92266@gmail.com>
Cc: dri-devel@lists.freedesktop.org, danielt@kernel.org
Subject: Re: [PATCH] backlight: ktd253: fix comment typo
Date: Wed, 16 Sep 2026 11:47:40 +0100	[thread overview]
Message-ID: <20260916104740.GO11487@google.com> (raw)
In-Reply-To: <CAF9RqJ64goBHhq3aC_FeGuzcRv2z1fRUyYL5hE=HPN7MsAw7RA@mail.gmail.com>

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

      reply	other threads:[~2026-09-16 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:56 [PATCH] backlight: ktd253: fix comment typo Ruslan Vagner
2026-09-16 10:47 ` Lee Jones [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260916104740.GO11487@google.com \
    --to=lee@kernel.org \
    --cc=danielt@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=rusya92266@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.