From: Thomas Renninger <trenn@suse.de>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: "jdelvare@novell.com" <jdelvare@novell.com>,
"Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Guenter Roeck <guenter.roeck@ericsson.com>
Subject: Re: thermal: Avoid CONFIG_NET compile dependency
Date: Tue, 25 Jan 2011 10:20:02 +0100 [thread overview]
Message-ID: <201101251020.03299.trenn@suse.de> (raw)
In-Reply-To: <D6D887BA8C9DFF48B5233887EF046541094488BDF5@bgsmsx502.gar.corp.intel.com>
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
next prev parent reply other threads:[~2011-01-25 9:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 10:52 thermal: Avoid CONFIG_NET compile dependency R, Durgadoss
2011-01-21 12:12 ` Thomas Renninger
2011-01-24 1:22 ` Zhang Rui
2011-01-24 4:39 ` R, Durgadoss
2011-01-24 10:35 ` Thomas Renninger
2011-01-24 13:07 ` Thermal kernel events API to userspace - Was: " Thomas Renninger
2011-01-24 16:07 ` Henrique de Moraes Holschuh
2011-01-25 7:57 ` Zhang Rui
2011-01-25 10:12 ` Thomas Renninger
2011-01-25 16:10 ` Henrique de Moraes Holschuh
2011-01-26 7:14 ` Zhang, Rui
2011-01-26 21:28 ` Henrique de Moraes Holschuh
2011-01-25 15:51 ` Henrique de Moraes Holschuh
2011-01-25 4:47 ` R, Durgadoss
2011-01-25 9:20 ` Thomas Renninger [this message]
2011-01-25 9:45 ` R, Durgadoss
2011-01-25 9:48 ` Jean Delvare
2011-01-25 13:43 ` Guenter Roeck
2011-01-25 16:18 ` Thomas Renninger
2011-01-25 16:25 ` Guenter Roeck
2011-01-27 9:48 ` Thomas Renninger
2011-01-27 13:34 ` R, Durgadoss
2011-01-27 13:59 ` Thomas Renninger
2011-01-25 7:54 ` Zhang Rui
2011-01-25 8:43 ` R, Durgadoss
2011-01-24 0:34 ` Zhang Rui
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=201101251020.03299.trenn@suse.de \
--to=trenn@suse.de \
--cc=durgadoss.r@intel.com \
--cc=fenghua.yu@intel.com \
--cc=guenter.roeck@ericsson.com \
--cc=jdelvare@novell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 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.