From: Rene Herman <rene.herman@keyaccess.nl>
To: Jean Delvare <khali@linux-fr.org>
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>,
linux-acpi@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
"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 16:06:20 +0200 [thread overview]
Message-ID: <485FADDC.4010108@keyaccess.nl> (raw)
In-Reply-To: <20080623154715.3ac8e984@hyperion.delvare>
On 23-06-08 15:47, Jean Delvare wrote:
>> This cannot be the reason, because it's not wrong. We just need a device
>> backlink. Basically, any single one will do. It's just about keeping
>> lm-sensors 2 happy.
>
> Your patch _is_ wrong. You make the device link point to _one_ of the
> devices that belong to the thermal zone, arbitrarily. If the device is
> removed before the thermal zone itself is, what happens?
As Zhang Rui said, this cannot happen in reality. I'll stop talking to
you. Kernel side, it's not your problem anyway, it's an ACPI Thermal
Zone one. Guess I'll go ask the 2.6.26 release manager if he feels that
breaking existing lm-sensors 2 userspace systems is acceptable. I myself
obviously know how to fix things by now.
Admittedly I need to find another hobby because the regularity with
which people on this list piss me off is definitely disturbing. I also
have this depressing notion that it might just be people pissing me off
with frightening regularity period, but oh well.
Gardening... maybe I'll do gardening now.
Rene.
next prev parent reply other threads:[~2008-06-23 14:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 0:47 LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors 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
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 [this message]
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=485FADDC.4010108@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=j.w.r.degoede@hhs.nl \
--cc=khali@linux-fr.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--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