From: Jagadeesh Yalapalli <jagadeesharm14@gmail.com>
To: William Hubbs <w.d.hubbs@gmail.com>
Cc: Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
Jagadeesh Yalapalli <jagadeesh.yalapalli@einfochips.com>
Subject: [PATCH v1] speakup: Replace u_short with u16 for spk_chartab
Date: Wed, 4 Jun 2025 13:58:36 +0000 [thread overview]
Message-ID: <20250604135846.46184-1-jagadeesharm14@gmail.com> (raw)
From: Jagadeesh Yalapalli <jagadeesh.yalapalli@einfochips.com>
The spk_chartab array was previously declared as `u_short`,
which is a non-standard type and may vary in size across platforms.
Replace it with `u16` to ensure consistent 16-bit width and improve
code portability and readability.
Signed-off-by: Jagadeesh Yalapalli <jagadeesh.yalapalli@einfochips.com>
---
drivers/accessibility/speakup/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/accessibility/speakup/main.c b/drivers/accessibility/speakup/main.c
index e68cf1d83787..34c7cb6a9b43 100644
--- a/drivers/accessibility/speakup/main.c
+++ b/drivers/accessibility/speakup/main.c
@@ -187,7 +187,7 @@ char *spk_default_chars[256] = {
* initialized to default_chartab and user selectable via
* /sys/module/speakup/parameters/chartab
*/
-u_short spk_chartab[256];
+u16 spk_chartab[256];
static u_short default_chartab[256] = {
B_CTL, B_CTL, B_CTL, B_CTL, B_CTL, B_CTL, B_CTL, B_CTL, /* 0-7 */
--
2.43.0
next reply other threads:[~2025-06-04 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 13:58 Jagadeesh Yalapalli [this message]
2025-06-04 14:58 ` Samuel Thibault
2025-06-05 5:08 ` [PATCH v2] speakup: Standardize character attribute types to u16 Jagadeesh Yalapalli
2025-06-07 17:15 ` Samuel Thibault
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=20250604135846.46184-1-jagadeesharm14@gmail.com \
--to=jagadeesharm14@gmail.com \
--cc=chris@the-brannons.com \
--cc=jagadeesh.yalapalli@einfochips.com \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=tglx@linutronix.de \
--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®