The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
	Chris Brannon <chris@the-brannons.com>,
	Kirk Reiser <kirk@reisers.ca>,
	speakup@linux-speakup.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] speakup: Fix spelling mistake "windo" -> "window"
Date: Mon, 17 Apr 2023 20:33:26 +0200	[thread overview]
Message-ID: <20230417183326.ylyd5xpog7dydw55@begin> (raw)
In-Reply-To: <20230417183203.54388-1-colin.i.king@gmail.com>

Colin Ian King, le lun. 17 avril 2023 19:32:03 +0100, a ecrit:
> There is a spelling mistake in a literal string. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>

Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

> ---
>  drivers/accessibility/speakup/i18n.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/accessibility/speakup/i18n.c b/drivers/accessibility/speakup/i18n.c
> index d62079b1661f..554bf81f2c1c 100644
> --- a/drivers/accessibility/speakup/i18n.c
> +++ b/drivers/accessibility/speakup/i18n.c
> @@ -31,7 +31,7 @@ static char *speakup_default_msgs[MSG_LAST_INDEX] = {
>  	[MSG_CURSORING_OFF] = "cursoring off",
>  	[MSG_CURSORING_ON] = "cursoring on",
>  	[MSG_HIGHLIGHT_TRACKING] = "highlight tracking",
> -	[MSG_READ_WINDOW] = "read windo",
> +	[MSG_READ_WINDOW] = "read window",
>  	[MSG_READ_ALL] = "read all",
>  	[MSG_EDIT_DONE] = "edit done",
>  	[MSG_WINDOW_ALREADY_SET] = "window already set, clear then reset",
> -- 
> 2.30.2
> 

      reply	other threads:[~2023-04-17 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 18:32 [PATCH] speakup: Fix spelling mistake "windo" -> "window" Colin Ian King
2023-04-17 18:33 ` Samuel Thibault [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=20230417183326.ylyd5xpog7dydw55@begin \
    --to=samuel.thibault@ens-lyon.org \
    --cc=chris@the-brannons.com \
    --cc=colin.i.king@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox