From: Denis Pauk <pauk.denis@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: pauk.denis@gmail.com, linux@roeck-us.net, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] hwmon: (nct6775) Fix ROG B550-XE WIFI and Pro B660M-C D4 names
Date: Thu, 23 Mar 2023 23:27:50 +0200 [thread overview]
Message-ID: <20230323212751.2474-2-pauk.denis@gmail.com> (raw)
In-Reply-To: <20230323212751.2474-1-pauk.denis@gmail.com>
ROG STRIX B550-XE GAMING WIFI motherboard is incorrectly named as
ROG STRIX B550-XE GAMING (WI-FI).
Pro B660M-C D4 motherboard is incorrectly named as
Pro B660M-C-D4.
Validated by dmidecode output from https://github.com/linuxhw/DMI/
Link: https://bugzilla.kernel.org/show_bug.cgi?id=204807
Signed-off-by: Denis Pauk <pauk.denis@gmail.com>
---
drivers/hwmon/nct6775-platform.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/nct6775-platform.c b/drivers/hwmon/nct6775-platform.c
index 5ba888b7eb8c8..9a7ad64c2cc3c 100644
--- a/drivers/hwmon/nct6775-platform.c
+++ b/drivers/hwmon/nct6775-platform.c
@@ -1090,7 +1090,7 @@ static const char * const asus_wmi_boards[] = {
"ROG STRIX B550-F GAMING (WI-FI)",
"ROG STRIX B550-F GAMING WIFI II",
"ROG STRIX B550-I GAMING",
- "ROG STRIX B550-XE GAMING (WI-FI)",
+ "ROG STRIX B550-XE GAMING WIFI",
"ROG STRIX X570-E GAMING",
"ROG STRIX X570-E GAMING WIFI II",
"ROG STRIX X570-F GAMING",
@@ -1147,7 +1147,7 @@ static const char * const asus_msi_boards[] = {
"PRIME Z590-V",
"PRIME Z590M-PLUS",
"Pro B660M-C",
- "Pro B660M-C-D4",
+ "Pro B660M-C D4",
"Pro WS W680-ACE",
"Pro WS W680-ACE IPMI",
"ProArt B650-CREATOR",
--
2.39.2
next prev parent reply other threads:[~2023-03-23 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 21:27 [PATCH 1/3] hwmon: (nct6775) Sort ASUS board list Denis Pauk
2023-03-23 21:27 ` Denis Pauk [this message]
2023-03-23 21:27 ` [PATCH 3/3] hwmon: (nct6775) update ASUS WMI monitoring list B360/H410/H610/Z390 Denis Pauk
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=20230323212751.2474-2-pauk.denis@gmail.com \
--to=pauk.denis@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®