From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v2 1/1] hwmon: Updated documentation on
Date: Tue, 26 May 2009 09:16:02 +0000 [thread overview]
Message-ID: <20090526111602.251b9b99@hyperion.delvare> (raw)
In-Reply-To: <9EE81EBECB70824985BE0EDA8DC9B515021B3458@VIECLEX01.frequentis.frq>
On Tue, 26 May 2009 11:01:26 +0200, Hans de Goede wrote:
> On 05/25/2009 10:15 PM, Engelmayer Christian wrote:
> > From: Christian Engelmayer<christian.engelmayer@frequentis.com>
> >
> > Added fan limit alarm 'max_alarm' to the alarm section.
> >
>
> Looks good to me now,
>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
I've applied the patch now. Please note that I did have to edit it
manually so that it would apply. Christian, please fix/setup your
e-mail client so that it doesn't wrap long lines.
One thing I am curious about is how we can have fan[1-*]_max_alarm
while we do not have fan[1-*]_max according to our documentation. Some
drivers still seem to implement this feature (dme1737, adt7470,
applesmc) so we should document it, whoulsn't we?
But the max6650 driver, which is what Christian is working on, does not
have this feature, it doesn't even have fan1_min as far as I can see.
This makes me curious about what the fan1_max_alarm and fan1_min_alarm
flags are supposed to mean for the MAX6650/1 device? Apparently not what
Documentation/hwmon/sysfs-interface says... which would be kind of
problematic.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-05-26 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 20:15 [lm-sensors] [PATCH v2 1/1] hwmon: Updated documentation on alarms Engelmayer Christian
2009-05-26 9:01 ` [lm-sensors] [PATCH v2 1/1] hwmon: Updated documentation on Hans de Goede
2009-05-26 9:16 ` Jean Delvare [this message]
2009-05-26 10:06 ` Engelmayer Christian
2009-05-27 15:29 ` Jean Delvare
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=20090526111602.251b9b99@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.