From: Jean Delvare <khali@linux-fr.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
Hans de Goede <j.w.r.degoede@hhs.nl>,
linux-acpi@vger.kernel.org,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org
Subject: Re: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors
Date: Mon, 23 Jun 2008 13:06:01 +0200 [thread overview]
Message-ID: <20080623130601.7715773e@hyperion.delvare> (raw)
In-Reply-To: <1214185482.3001.45.camel@rzhang-dt.sh.intel.com>
Hi Rui,
On Mon, 23 Jun 2008 09:44:42 +0800, Zhang Rui wrote:
> On Mon, 2008-06-23 at 05:58 +0800, Rene Herman wrote:
> > On 22-06-08 20:25, Rene Herman wrote:
> >
> > > Another way to solve it _could_ be to just make up a device link if
> > > something generic is available so that sensors doesn't trip over it
> > > in the first place but I don't know if that's a good option. You
> > > might.
> >
> > This also works for me and, if correct, is ofcourse better than the
> > CONFIG option. Wants a comment from the thermal_zone side (for which
> > Zhang Rui seems the correct CC?) though.
> Hi, Rene and Hans,
>
> Thank you for your efforts on this issue and sorry for the late
> response, I did not check my email during the whole weekend.
>
> About the hwmon ABI, after the device symbol link is created, are there
> any other ABIs required in the device node?
Not that I know of. The code currently in the kernel works just fine
with both lm-sensors SVN trunk (which will become 2.10.7 soon) and
3.0.2 as far as I can see.
> If no, this patch seems to work, although it might break if the first
> registered ACPI thermal zone device is unregistered, which ONLY happens
> theoretically.
If I remember correctly, there are more than one device in a given
thermal zone, so having a link pointing to one of them would create an
asymmetry. This basically means that nobody can use the device link in
question, so there's no point in creating it from a functional point of
view. If the goal is simply to solve the breakage that was reported by
Rene, the bug is in libsensors, so that' where it must be fixed (and
actually it already is.)
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2008-06-23 11:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 0:47 Rene Herman
2008-06-22 7:28 ` [lm-sensors] " Hans de Goede
2008-06-22 13:15 ` [REGRESSION, ABI] " Rene Herman
2008-06-22 13:23 ` Rene Herman
2008-06-22 14:29 ` [lm-sensors] [REGRESSION, ABI] " Hans de Goede
2008-06-22 15:26 ` Rene Herman
2008-06-22 18:07 ` Hans de Goede
2008-06-22 18:25 ` Rene Herman
2008-06-22 21:58 ` Rene Herman
2008-06-23 1:44 ` Zhang Rui
2008-06-23 5:21 ` Hans de Goede
2008-06-23 10:40 ` Rene Herman
2008-06-23 11:06 ` Jean Delvare [this message]
2008-06-23 10:56 ` Jean Delvare
2008-06-23 17:54 ` [lm-sensors] [REGRESSION, ABI] " Len Brown
2008-06-23 19:54 ` Jean Delvare
2008-06-23 20:07 ` [lm-sensors] [REGRESSION, ABI] " Rene Herman
2008-06-23 20:24 ` Rene Herman
2008-06-22 15:43 ` Rene Herman
2008-06-23 10:08 ` Jean Delvare
2008-06-23 10:24 ` Rene Herman
2008-06-23 11:57 ` Jean Delvare
2008-06-23 12:35 ` Rene Herman
2008-06-23 13:47 ` Jean Delvare
2008-06-23 14:06 ` Rene Herman
2008-06-23 14:31 ` Matthew Garrett
2008-06-23 17:10 ` Rene Herman
2008-06-23 13:51 ` Hans de Goede
2008-06-22 7:30 ` [lm-sensors] " Hans de Goede
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=20080623130601.7715773e@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=j.w.r.degoede@hhs.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rene.herman@keyaccess.nl \
--cc=rui.zhang@intel.com \
/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
Powered by JetHome