From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Renninger Subject: Re: thermal: Avoid CONFIG_NET compile dependency Date: Tue, 25 Jan 2011 10:20:02 +0100 Message-ID: <201101251020.03299.trenn@suse.de> References: <201101241135.23576.trenn@suse.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from cantor2.suse.de ([195.135.220.15]:42421 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751695Ab1AYJUG (ORCPT ); Tue, 25 Jan 2011 04:20:06 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "R, Durgadoss" Cc: "jdelvare@novell.com" , "Zhang, Rui" , Len Brown , "linux-acpi@vger.kernel.org" , "Yu, Fenghua" , Guenter Roeck On Tuesday, January 25, 2011 05:47:56 AM R, Durgadoss wrote: > Hi Thomas, ... > If we make the coretemp register with the thermal framework, we have to modify > the sysfs _store and _show functions a bit. Hence, the coretemp people were not > very happy with the idea of making coretemp register with the thermal framework. > So, I just added support to the core thresholds, and when current > temperature crosses them, it sends a netlink event. Can you give a pointer to this discussion if there is any. I think a generic thermal netlink interface can get implemented separately, best without looking at any specific driver implementation. Best would be to revert the current patch and send a more generic implementation with at least these in CC (or other lists maintaining drivers who might make use of it): platform-driver-x86@vger.kernel.org linux-pm@lists.linux-foundation.org Then people can bring in their needs and eventually come up with code making use of it. Thomas