From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: "Thomas, Sujith" <sujith.thomas@intel.com>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
"Zhang, Rui" <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
Jean Delvare <khali@linux-fr.org>, Len Brown <lenb@kernel.org>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: The new thermal management sysfs class, and hwmon
Date: Thu, 14 Feb 2008 14:08:55 +0000 [thread overview]
Message-ID: <20080214140855.GB12412@srcf.ucam.org> (raw)
In-Reply-To: <1202915450.7977.607.camel@queen.suse.de>
On Wed, Feb 13, 2008 at 04:10:50PM +0100, Thomas Renninger wrote:
> Why do you want to still export the temperature via ACPI sysfs paths
> then?
> Once it is there and userspace progs make use of it, you will have to
> maintain it forever and HAL is getting crazy and must take care about:
> - How to find the ACPI thermal node
> - Find the hwmon node
> - Both interfaces provide temeratures
> - Parse different output of temperature values (totally crazy)
>
Quite. There's still been no indication that anyone cares about fixing
this interface, and I'm upset that it was merged despite there being
clear and valid concerns about it. Do we have a commitment that it's
going to be cleaned up before final? If not, it should be pulled before
userspace starts depending on it. The only hardware where this currently
matters isn't going to be running 2.6.25 anyway.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-02-14 14:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 2:26 The new thermal management sysfs class, and hwmon Henrique de Moraes Holschuh
2008-02-03 9:31 ` Zhang Rui
2008-02-03 16:44 ` Mark M. Hoffman
2008-02-03 17:50 ` Henrique de Moraes Holschuh
2008-02-05 10:14 ` Thomas, Sujith
2008-02-05 13:57 ` Mark M. Hoffman
2008-02-05 14:55 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-07 7:01 ` Len Brown
2008-02-07 12:30 ` Henrique de Moraes Holschuh
2008-02-06 5:23 ` Thomas, Sujith
2008-02-13 15:10 ` Thomas Renninger
2008-02-14 14:08 ` Matthew Garrett [this message]
2008-02-15 11:04 ` Thomas, Sujith
2008-02-15 11:56 ` Matthew Garrett
2008-02-15 12:19 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-22 5:47 ` zhangrui
2008-02-22 8:00 ` [lm-sensors] " Hans de Goede
2008-02-22 8:33 ` Zhang, Rui
2008-02-22 10:54 ` Hans de Goede
2008-02-23 7:43 ` Len Brown
2008-02-23 8:29 ` Jean Delvare
2008-02-24 22:52 ` Zhang, Rui
2008-02-25 8:53 ` Hans de Goede
2008-02-23 20:39 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-07 6:41 ` Len Brown
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=20080214140855.GB12412@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=hughsient@gmail.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rui.zhang@intel.com \
--cc=sujith.thomas@intel.com \
--cc=trenn@suse.de \
/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