From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] hwmon: (asus-ec-sensors) add missing mutex path
Date: Tue, 24 Jan 2023 05:55:24 -0800 [thread overview]
Message-ID: <20230124135524.GA36884@roeck-us.net> (raw)
In-Reply-To: <20230121111728.168514-2-eugene.shalygin@gmail.com>
On Sat, Jan 21, 2023 at 12:17:28PM +0100, Eugene Shalygin wrote:
> Add missing mutex path for ProArt X570-CREATOR WIFI.
>
> Fixes: de8fbac5 (hwmon: (asus-ec-sensors) implement locking via the ACPI global lock)
> Signed-off-by: Eugene Shalygin <eugene.shalygin@gmail.com>
Applied.
The abbreviated SHA in Fixes: tags should include 12 SHA letters/digits.
I fixed that up, but please keep it in mind for future patches.
Thanks,
Guenter
> ---
> drivers/hwmon/asus-ec-sensors.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/asus-ec-sensors.c b/drivers/hwmon/asus-ec-sensors.c
> index a901e4e33d81..b4d65916b3c0 100644
> --- a/drivers/hwmon/asus-ec-sensors.c
> +++ b/drivers/hwmon/asus-ec-sensors.c
> @@ -299,6 +299,7 @@ static const struct ec_board_info board_info_pro_art_x570_creator_wifi = {
> .sensors = SENSOR_SET_TEMP_CHIPSET_CPU_MB | SENSOR_TEMP_VRM |
> SENSOR_TEMP_T_SENSOR | SENSOR_FAN_CPU_OPT |
> SENSOR_CURR_CPU | SENSOR_IN_CPU_CORE,
> + .mutex_path = ASUS_HW_ACCESS_MUTEX_ASMX,
> .family = family_amd_500_series,
> };
>
prev parent reply other threads:[~2023-01-24 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 11:17 [PATCH 0/1] hwmon: (asus-ec-sensors) add missing mutex path Eugene Shalygin
2023-01-21 11:17 ` [PATCH 1/1] " Eugene Shalygin
2023-01-24 13:55 ` Guenter Roeck [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=20230124135524.GA36884@roeck-us.net \
--to=linux@roeck-us.net \
--cc=eugene.shalygin@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).