From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] PATCH: add support for lm_sensors 3.0.0 to gkrellm
Date: Sun, 28 Oct 2007 14:05:13 +0000 [thread overview]
Message-ID: <20071028150513.6a8f296b@hyperion.delvare> (raw)
In-Reply-To: <472463E8.8060109@hhs.nl>
Hi Hans,
On Sun, 28 Oct 2007 11:26:48 +0100, Hans de Goede wrote:
> For those interested. I've made the patch so that gkrellm can be compiled
> against the new version (or the old) and so that the identification strings of
> the sensors do not change and thus old gkrellm configs will continue to work as is.
Random comments:
> + snprintf(sensor_path, sizeof (sensor_path), "%s:%s",
> + name->prefix, name->path ? name->path : "NULL");
name->path can't actually be NULL. BTW, I wonder why you need
name->path at all. This is meant for libsensors internal use,
applications shouldn't care about it. Also note that the path is not
guaranteed to be consistent across reboots.
> + /* failsafe tests, will bus type and nr fit in 8 bits
> + signed and addr fit in 16 bits signed ?
> + */
Unfortunately not: for SPI, the bus number can require 16 bits. It's
due to the weird way spi-core uses to number buses dynamically, it
should really be addressed someday, but at the moment it isn't.
> I've also send this upstream, and its available here:
> http://people.atrpms.net/~hdegoede/gkrellm-2.3.0-libsensors4.patch
Note that I've stopped referring to "libsensors4" after I realized it
could cause confusion. While the binary file will be named
"libsensors.so.4", the library version will be advertised as
"libsensors 3.0.0". So for example I've renamed the xsensors patch to:
xsensors-0.60-libsensors-3.patch
And I suggest that you do the same. The soname is an internal detail
end users don't even need to know.
> The later is to be able to put up a link on the download page for the 3.0.0
> RC's from the wiki, I haven't done this yet as this patch will not work with
> rc2, it requires current svn.
rc3 is released now, so you could proceed. However you'll need special
permissions to edit the Download page. So I can either grant you these
permissions if you want, or I can add the link for you if you prefer.
--
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:[~2007-10-28 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 10:26 [lm-sensors] PATCH: add support for lm_sensors 3.0.0 to gkrellm Hans de Goede
2007-10-28 14:05 ` Jean Delvare [this message]
2007-10-28 14:23 ` Hans de Goede
2007-10-28 21:16 ` 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=20071028150513.6a8f296b@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.