From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: huangli05 <huangli05@inspur.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: speakup: modify syntax errors in comments
Date: Tue, 19 Sep 2023 10:19:36 +0200 [thread overview]
Message-ID: <20230919081936.he5ghmgjeiu7264h@begin> (raw)
In-Reply-To: <20230919074206.36909-1-huangli05@inspur.com>
huangli05, le mar. 19 sept. 2023 15:42:06 +0800, a ecrit:
> From: “huangli05“ <huangli05@inspur.com>
>
> Change "/* We want to set the the speech synthesis" to "/* We want to set the speech synthesis"
>
> Signed-off-by: “huangli05“ <huangli05@inspur.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> drivers/accessibility/speakup/speakup_soft.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/accessibility/speakup/speakup_soft.c b/drivers/accessibility/speakup/speakup_soft.c
> index 6d446824677b..6549bfb96e7f 100644
> --- a/drivers/accessibility/speakup/speakup_soft.c
> +++ b/drivers/accessibility/speakup/speakup_soft.c
> @@ -446,7 +446,7 @@ static int softsynth_adjust(struct spk_synth *synth, struct st_var_header *var)
> if (var->var_id != PUNC_LEVEL)
> return 0;
>
> - /* We want to set the the speech synthesis punctuation level
> + /* We want to set the speech synthesis punctuation level
> * accordingly, so it properly tunes speaking A_PUNC characters */
> var_data = var->data;
> if (!var_data)
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-09-19 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 7:42 [PATCH] staging: speakup: modify syntax errors in comments huangli05
2023-09-19 8:19 ` Samuel Thibault [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 2:13 huangli05
2023-09-21 7:34 ` Greg KH
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=20230919081936.he5ghmgjeiu7264h@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=chris@the-brannons.com \
--cc=huangli05@inspur.com \
--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