From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Better generic print fault handling
Date: Sat, 07 Jul 2007 15:49:35 +0000 [thread overview]
Message-ID: <20070707174935.7d4e56e4@hyperion.delvare> (raw)
On Thu, 5 Jul 2007 23:03:12 +0200 (CEST), lm-sensors-notify@lm-sensors.org wrote:
> Author: jwrdegoede
> Date: Thu Jul 5 23:03:06 2007
> New Revision: 4559
> Changeset: http://lm-sensors.org/changeset/4559
>
> Modified:
> lm-sensors/branches/lm-sensors-3.0.0/prog/sensors/chips.c
> lm-sensors/branches/lm-sensors-3.0.0/prog/sensors/chips_generic.c
>
> Log:
> Better generic print fault handling
OK, it works (tested with an ADM1032 in both degrees C and F) but I
can't say I find using HUGE_VAL particularly aesthetic. I have to admit
that this was certainly the quickest way to implement proper
temperature fault handling without changing the temp_print_info()
signature. But OTOH, temp_print_info() is only called once, so changing
its signature wouldn't be a big problem.
I guess that the main problem here is that we have an artificial split
of temp_print_info() outside of the generic temperature printing
function, while we shouldn't. This explains in part why the this
generic temperature printing function doesn't look quite good.
This is something that can be fixed later on though, so I won't be
working on it now. So I've created a new milestone in trac (3.0.1), and
I've created ticket #2231 for this.
Oh, and I also created new components "sensors" and "libsensors" for
trac tickets. The component list we had so far didn't make much sense
to me, I never know what to choose.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2007-07-07 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 15:49 Jean Delvare [this message]
2007-07-07 16:38 ` [lm-sensors] Better generic print fault handling Hans de Goede
2007-07-07 19:04 ` 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=20070707174935.7d4e56e4@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.