public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
	lm-sensors <lm-sensors@lm-sensors.org>,
	Hans de Goede <j.w.r.degoede@hhs.nl>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 2/3] thermal: add hwmon sys I/F
Date: Mon, 7 Apr 2008 12:22:42 +0200	[thread overview]
Message-ID: <20080407122242.36aa4ddb@hyperion.delvare> (raw)
In-Reply-To: <20080407114648.46cec5c6@hyperion.delvare>

Quoting myself...

On Mon, 7 Apr 2008 11:46:48 +0200, Jean Delvare wrote:
> One thing that worries me is the hwmon device name. It comes directly
> from the thermal zone's type ("ACPI thermal zone" in the ACPI case".)
> We have no control over that name, while libsensors makes some
> assumptions on it. For example it assumes that there is no dash in a
> hwmon device name. So far, all hwmon device names also didn't have
> spaces, nor uppercase letters, and were much shorter (ACPI thermal zone
> would be something like "acpi_tz".) I hope that applications didn't
> make too many assumptions on length or content...
> 
> I'm not sure yet if and how we want to address this problem. Maybe we
> could have a "short name" field in struct thermal_zone_device. Or
> alternatively I could add a conversion function to libsensors, that
> would convert "ACPI thermal zone" to "acpi_thermal_zone". The latter
> approach doesn't help with the length, but at least it normalizes the
> character set.

Oh, I now see that you addressed the problem in patch 3/3, so you can
forget about what I wrote above. Thank you :)

-- 
Jean Delvare

      reply	other threads:[~2008-04-07 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02  8:08 [PATCH 2/3] thermal: add hwmon sys I/F Zhang, Rui
2008-04-07  9:46 ` Jean Delvare
2008-04-07 10:22   ` Jean Delvare [this message]

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=20080407122242.36aa4ddb@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox