From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm-sens 2.10.5 fschmd support
Date: Fri, 12 Oct 2007 08:46:44 +0000 [thread overview]
Message-ID: <470F3474.5040809@hhs.nl> (raw)
Hi all,
I've just committed support for the new fschmd to trunk, so that it will be
available in 2.10.5
It would be much appreciated if people who have an fsc chip could test the
current trunk with it. I've been very carefull to make sure there will be no
regressions.
Also a quick review would be nice.
Here is the changelog entry:
This patchset adds support for the new fschmd driver, while keeping
compatibility with the old:
-The feature lists for the fscpos, fscscy and fscher have been extended to
include the new features exported by the fschmd driver
-Feature lists for the fschmd and fschrc have been added
-The print functions in "sensors" for the fscpos, fscscy and fscher have
been modified to detect on which driver they run, on the old driver
behaviour is unmodified, on the new driver the non sysfs-interface
compliant attributes are not used and the extra features exported by the
new driver are shown.
-print functions for the fschmd and fschrc have been added to "sensors"
-mapping from the non standard sysfs attr name fan#_ripple used by the old
fscpos, fscscy and fscher drivers to the standard fan#_div used by the
fschmd driver has been added to getsysname() using altsysname.
Thanks & Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2007-10-12 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 8:46 Hans de Goede [this message]
2007-10-13 17:14 ` [lm-sensors] lm-sens 2.10.5 fschmd support Jean Delvare
2007-10-14 11:57 ` Hans de Goede
2007-10-15 13:17 ` 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=470F3474.5040809@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.