From: Guenter Roeck <linux@roeck-us.net>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: Add missing HWMON_T_ALARM
Date: Fri, 17 Mar 2017 06:43:54 -0700 [thread overview]
Message-ID: <20170317134354.GA16340@roeck-us.net> (raw)
In-Reply-To: <1489706936-26535-1-git-send-email-peterhuewe@gmx.de>
On Fri, Mar 17, 2017 at 12:28:56AM +0100, Peter Huewe wrote:
> Unfortunately the HWMON_T_ALARM define was missing,
> although the associated entry was present in hwmon_temp_attributes.
> This is needed to convert drivers to the new interface which use channel
> based alarms.
>
Good catch. Applied.
Thanks,
Guenter
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> ---
> include/linux/hwmon.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/hwmon.h b/include/linux/hwmon.h
> index 78d59dba563e..88b673749121 100644
> --- a/include/linux/hwmon.h
> +++ b/include/linux/hwmon.h
> @@ -88,6 +88,7 @@ enum hwmon_temp_attributes {
> #define HWMON_T_CRIT_HYST BIT(hwmon_temp_crit_hyst)
> #define HWMON_T_EMERGENCY BIT(hwmon_temp_emergency)
> #define HWMON_T_EMERGENCY_HYST BIT(hwmon_temp_emergency_hyst)
> +#define HWMON_T_ALARM BIT(hwmon_temp_alarm)
> #define HWMON_T_MIN_ALARM BIT(hwmon_temp_min_alarm)
> #define HWMON_T_MAX_ALARM BIT(hwmon_temp_max_alarm)
> #define HWMON_T_CRIT_ALARM BIT(hwmon_temp_crit_alarm)
> --
> 2.7.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-03-17 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 23:28 [PATCH] hwmon: Add missing HWMON_T_ALARM Peter Huewe
2017-03-17 13:43 ` 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=20170317134354.GA16340@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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