From: Guenter Roeck <linux@roeck-us.net>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jean Delvare <jdelvare@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: Fix HWMON_P_MIN_ALARM mask
Date: Wed, 2 Oct 2019 06:37:27 -0700 [thread overview]
Message-ID: <20191002133727.GA15583@roeck-us.net> (raw)
In-Reply-To: <20190924124945.491326-2-nuno.sa@analog.com>
On Tue, Sep 24, 2019 at 02:49:43PM +0200, Nuno Sá wrote:
> Both HWMON_P_MIN_ALARM and HWMON_P_MAX_ALARM were using
> BIT(hwmon_power_max_alarm).
>
> Fixes: aa7f29b07c870 ("hwmon: Add support for power min, lcrit, min_alarm and lcrit_alarm")
> CC: <stable@vger.kernel.org>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
Applied.
Thanks,
Guenter
> ---
> include/linux/hwmon.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/hwmon.h b/include/linux/hwmon.h
> index 04c36b7a61dd..72579168189d 100644
> --- a/include/linux/hwmon.h
> +++ b/include/linux/hwmon.h
> @@ -235,7 +235,7 @@ enum hwmon_power_attributes {
> #define HWMON_P_LABEL BIT(hwmon_power_label)
> #define HWMON_P_ALARM BIT(hwmon_power_alarm)
> #define HWMON_P_CAP_ALARM BIT(hwmon_power_cap_alarm)
> -#define HWMON_P_MIN_ALARM BIT(hwmon_power_max_alarm)
> +#define HWMON_P_MIN_ALARM BIT(hwmon_power_min_alarm)
> #define HWMON_P_MAX_ALARM BIT(hwmon_power_max_alarm)
> #define HWMON_P_LCRIT_ALARM BIT(hwmon_power_lcrit_alarm)
> #define HWMON_P_CRIT_ALARM BIT(hwmon_power_crit_alarm)
next prev parent reply other threads:[~2019-10-02 13:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 12:49 [PATCH 0/3] LTC2947 support Nuno Sá
2019-09-24 12:49 ` [PATCH 1/3] hwmon: Fix HWMON_P_MIN_ALARM mask Nuno Sá
2019-10-02 13:37 ` Guenter Roeck [this message]
2019-09-24 12:49 ` [PATCH 2/3] hwmon: Add support for ltc2947 Nuno Sá
2019-10-03 4:14 ` Guenter Roeck
2019-10-04 7:45 ` Sa, Nuno
2019-10-04 15:06 ` Guenter Roeck
2019-10-07 12:25 ` Sa, Nuno
2019-10-07 12:44 ` Guenter Roeck
2019-10-07 14:51 ` Sa, Nuno
2019-10-10 7:13 ` Sa, Nuno
2019-10-10 15:21 ` Guenter Roeck
2019-10-11 6:59 ` Sa, Nuno
2019-09-24 12:49 ` [PATCH 3/3] dt-bindings: iio: Add ltc2947 documentation Nuno Sá
2019-10-02 14:19 ` Rob Herring
2019-10-02 15:09 ` Sa, Nuno
2019-10-02 19:06 ` Rob Herring
2019-10-04 14:58 ` Sa, Nuno
2019-10-04 15:23 ` Rob Herring
2019-10-08 14:20 ` Sa, Nuno
2019-09-26 10:17 ` [PATCH 0/3] LTC2947 support Sa, Nuno
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=20191002133727.GA15583@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nuno.sa@analog.com \
--cc=robh+dt@kernel.org \
--cc=stable@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).