From: Hemanth Selam <hemanth.selam@gmail.com>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: corentin.chary@gmail.com, luke@ljones.dev,
denis.benato@linux.dev, W_Armin@gmx.de,
eric.piel@tremplin-utc.net, kenneth.t.chan@gmail.com,
jlee@suse.com, srinivas.pandruvada@linux.intel.com,
mpearson-lenovo@squebb.ca, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 8/8] platform/x86: uniwill-laptop: Fix typo in the kbd LED brightness comment
Date: Thu, 10 Sep 2026 10:14:43 +0530 [thread overview]
Message-ID: <5899c28bcbdc04c0c07ae3f1bf8501e928e7d4dd.1789015364.git.hemanth.selam@gmail.com> (raw)
In-Reply-To: <cover.1789015364.git.hemanth.selam@gmail.com>
Correct "device-specfic" to "device-specific" in the comment on
restoring the default RGB value. Comment only, no functional change.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
Reviewed-by: Mark Pearson <mpearson-lenovo@squebb.ca>
Reviewed-by: Denis Benato <denis.benato@linux.dev>
---
drivers/platform/x86/uniwill/uniwill-acpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
index 7a2eeaec4c96..eeead0159828 100644
--- a/drivers/platform/x86/uniwill/uniwill-acpi.c
+++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
@@ -1705,7 +1705,7 @@ static int uniwill_kbd_led_mc_brightness_set(struct led_classdev *led_cdev,
/*
* The EC interprets a RGB value of 0x000000 as a command to restore
- * the device-specfic default RGB value. Work around this by writing
+ * the device-specific default RGB value. Work around this by writing
* a RGB value of 0x010101 (faint white) instead.
*/
if (data->kbd_led_mc_subled_info[0].intensity == 0 &&
--
2.48.1
next prev parent reply other threads:[~2026-09-10 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 4:44 [PATCH v2 0/8] platform/x86: Fix typos in comments Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 1/8] platform/x86: asus-laptop: Fix typo in infos_show() comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 2/8] platform/x86: asus-nb-wmi: Fix typo in asus_nb_wmi_quirks() comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 3/8] platform/x86: hp_accel: Fix typo in lis3lv02d_acpi_write() comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 4/8] platform/x86/intel/tpmi: Fix typo in TPMI_FEATURE_NAME_LEN comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 5/8] platform/x86: msi-laptop: Fix typo in struct quirk_entry comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 6/8] platform/x86: panasonic-laptop: Fix typo in the file history comment Hemanth Selam
2026-09-10 4:44 ` [PATCH v2 7/8] platform/x86: samsung-laptop: Fix typo in sabi_configs comment Hemanth Selam
2026-09-10 4:44 ` Hemanth Selam [this message]
2026-09-16 10:36 ` [PATCH v2 0/8] platform/x86: Fix typos in comments Ilpo Järvinen
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=5899c28bcbdc04c0c07ae3f1bf8501e928e7d4dd.1789015364.git.hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=W_Armin@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=eric.piel@tremplin-utc.net \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jlee@suse.com \
--cc=kenneth.t.chan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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®