From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: linux-kernel@vger.kernel.org
Cc: Eugene Shalygin <eugene.shalygin@gmail.com>,
Denis Pauk <pauk.denis@gmail.com>,
matt-testalltheway <sefoci9222@rerunway.com>,
Kamil Dudka <kdudka@redhat.com>,
Robert Swiecki <robert@swiecki.net>,
Kamil Pietrzak <kpietrzak@disroot.org>, Igor <igor@svelig.com>,
Tor Vic <torvic9@mailbox.org>, Poezevara <nephartyz@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org
Subject: [PATCH 0/3] hwmon: add ASUS Pro WS X570-ACE support
Date: Sun, 3 Oct 2021 15:33:41 +0200 [thread overview]
Message-ID: <20211003133344.9036-1-oleksandr@natalenko.name> (raw)
Based on hwmon-next + [1].
ASUS Pro WS X570-ACE board carries an nct6775 chip, which needs proper
support without kernel command line quirk. Also, the sensors of this
board can be monitored via BREC WMI method.
This submission addresses both issues.
Please review.
Thanks.
[1] https://lore.kernel.org/lkml/20211002210857.709956-1-pauk.denis@gmail.com/
Oleksandr Natalenko (3):
hwmon: (nct6775) add Pro WS X570-ACE
hwmon: (asus_wmi_sensors) split out T_Sensor
hwmon: (asus_wmi_sensors) add Pro WS X570-ACE
drivers/hwmon/asus_wmi_sensors.c | 19 ++++++++++++++++---
drivers/hwmon/nct6775.c | 1 +
2 files changed, 17 insertions(+), 3 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-03 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 13:33 Oleksandr Natalenko [this message]
2021-10-03 13:33 ` [PATCH 1/3] hwmon: (nct6775) add Pro WS X570-ACE Oleksandr Natalenko
2021-10-08 14:13 ` Guenter Roeck
2021-10-03 13:33 ` [PATCH 2/3] hwmon: (asus_wmi_sensors) split out T_Sensor Oleksandr Natalenko
2021-10-11 14:25 ` Guenter Roeck
2021-10-03 13:33 ` [PATCH 3/3] hwmon: (asus_wmi_sensors) add Pro WS X570-ACE Oleksandr Natalenko
2021-10-03 17:30 ` [PATCH 0/3] hwmon: add ASUS Pro WS X570-ACE support Andy Shevchenko
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=20211003133344.9036-1-oleksandr@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=andriy.shevchenko@intel.com \
--cc=eugene.shalygin@gmail.com \
--cc=igor@svelig.com \
--cc=jdelvare@suse.com \
--cc=kdudka@redhat.com \
--cc=kpietrzak@disroot.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nephartyz@gmail.com \
--cc=pauk.denis@gmail.com \
--cc=robert@swiecki.net \
--cc=sefoci9222@rerunway.com \
--cc=torvic9@mailbox.org \
/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