From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Mushahid Hussain <mushi.shar@gmail.com>,
William Hubbs <w.d.hubbs@gmail.com>,
Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
speakup@linux-speakup.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] accessibility: use C99 array init
Date: Mon, 1 May 2023 03:32:19 +0200 [thread overview]
Message-ID: <20230501013219.e4ekzxgoequdlmsu@begin> (raw)
In-Reply-To: <20230501001617.9152-1-rdunlap@infradead.org>
Randy Dunlap, le dim. 30 avril 2023 17:16:17 -0700, a ecrit:
> Use C99 array initializer syntax for consistency with other array
> initializers around it and to eliminate a sparse warning:
>
> drivers/accessibility/speakup/main.c:1290:26: sparse: warning: obsolete array initializer, use C99 syntax
>
> Fixes: f43241aafedb ("accessibility: speakup: Specify spk_vars among module parameters")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Mushahid Hussain <mushi.shar@gmail.com>
> Cc: William Hubbs <w.d.hubbs@gmail.com>
> Cc: Chris Brannon <chris@the-brannons.com>
> Cc: Kirk Reiser <kirk@reisers.ca>
> Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
> Cc: speakup@linux-speakup.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Thanks!
> ---
> drivers/accessibility/speakup/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -- a/drivers/accessibility/speakup/main.c b/drivers/accessibility/speakup/main.c
> --- a/drivers/accessibility/speakup/main.c
> +++ b/drivers/accessibility/speakup/main.c
> @@ -1287,7 +1287,7 @@ static struct var_t spk_vars[NB_ID] = {
> [PUNC_LEVEL_ID] = { PUNC_LEVEL, .u.n = {NULL, 1, 0, 4, 0, 0, NULL} },
> [READING_PUNC_ID] = { READING_PUNC, .u.n = {NULL, 1, 0, 4, 0, 0, NULL} },
> [CURSOR_TIME_ID] = { CURSOR_TIME, .u.n = {NULL, 120, 50, 600, 0, 0, NULL} },
> - [SAY_CONTROL_ID] { SAY_CONTROL, TOGGLE_0},
> + [SAY_CONTROL_ID] = { SAY_CONTROL, TOGGLE_0},
> [SAY_WORD_CTL_ID] = {SAY_WORD_CTL, TOGGLE_0},
> [NO_INTERRUPT_ID] = { NO_INTERRUPT, TOGGLE_0},
> [KEY_ECHO_ID] = { KEY_ECHO, .u.n = {NULL, 1, 0, 2, 0, 0, NULL} },
>
prev parent reply other threads:[~2023-05-01 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 0:16 Randy Dunlap
2023-05-01 1:32 ` 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=20230501013219.e4ekzxgoequdlmsu@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=chris@the-brannons.com \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mushi.shar@gmail.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®