From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Subject: Re: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors Date: Mon, 23 Jun 2008 16:06:20 +0200 Message-ID: <485FADDC.4010108@keyaccess.nl> References: <485DA11C.7050906@keyaccess.nl> <485DFF35.6080008@hhs.nl> <485E505F.8010306@keyaccess.nl> <485E61DE.6020202@hhs.nl> <20080623120844.5f722aa6@hyperion.delvare> <485F79C6.20507@keyaccess.nl> <20080623135704.2980078c@hyperion.delvare> <485F9877.1060902@keyaccess.nl> <20080623154715.3ac8e984@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtpq1.groni1.gr.home.nl ([213.51.130.200]:56260 "EHLO smtpq1.groni1.gr.home.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752910AbYFWOFk (ORCPT ); Mon, 23 Jun 2008 10:05:40 -0400 In-Reply-To: <20080623154715.3ac8e984@hyperion.delvare> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Jean Delvare Cc: Hans de Goede , linux-acpi@vger.kernel.org, Zhang Rui , "Mark M. Hoffman" , Linux Kernel , lm-sensors@lm-sensors.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Date: Mon, 23 Jun 2008 14:06:20 +0000 Subject: Re: [lm-sensors] LMSENSORS: 2.6.26-rc, Message-Id: <485FADDC.4010108@keyaccess.nl> List-Id: References: <485DA11C.7050906@keyaccess.nl> <485DFF35.6080008@hhs.nl> <485E505F.8010306@keyaccess.nl> <485E61DE.6020202@hhs.nl> <20080623120844.5f722aa6@hyperion.delvare> <485F79C6.20507@keyaccess.nl> <20080623135704.2980078c@hyperion.delvare> <485F9877.1060902@keyaccess.nl> <20080623154715.3ac8e984@hyperion.delvare> In-Reply-To: <20080623154715.3ac8e984@hyperion.delvare> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jean Delvare Cc: Hans de Goede , linux-acpi@vger.kernel.org, Zhang Rui , "Mark M. Hoffman" , Linux Kernel , lm-sensors@lm-sensors.org 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. _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors