public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <jdelvare@suse.de>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] coretemp.0 folder contents changed
Date: Wed, 07 May 2014 05:10:58 -0700	[thread overview]
Message-ID: <536A22D2.5070104@roeck-us.net> (raw)
In-Reply-To: <20140507091308.227d8152@endymion.delvare>

On 05/07/2014 12:13 AM, Jean Delvare wrote:
> Hi Guenter,
>
> On Tue, 06 May 2014 06:32:15 -0700, Guenter Roeck wrote:
>> Can we implement a similar approach to network devices and make hwmon
>> path names (ie the /sys/class/hwmon/XXX path name) configurable via udev ?
>> Might be worth exploring.
>
> This is one possibility indeed. The good thing is that libsensors makes
> no assumption on hwmon class device names, so we can change the names
> without breaking any application which uses libsensors. Scripts
> accessing sysfs directly may break though (pwmconfig would, for
> example.)
>
> We'll have to be careful when choosing the new names, and make sure
> there is no name space collision. Network interface renaming has caused
> a great deal of trouble out there.
>
Agreed. I'll try to find some time to play with it.

> Another approach, which I have in mind for quite some time already but
> could never find the time to implement, would be a small helper binary
> which would look-up hwmon devices by libsensors-like name (and the
> other way around too.) Scripts could use it to benefit from libsensors
> persistent names.
>
Still needs that binary, though.

Guenter


  reply	other threads:[~2014-05-07 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 17:13 coretemp.0 folder contents changed Srinivas Pandruvada
2014-05-05 17:32 ` Guenter Roeck
2014-05-05 17:46   ` Srinivas Pandruvada
2014-05-06 11:55   ` [lm-sensors] " Jean Delvare
2014-05-06 13:32     ` Guenter Roeck
2014-05-07  7:13       ` Jean Delvare
2014-05-07 12:10         ` Guenter Roeck [this message]
2014-05-09  7:57           ` Jean Delvare
2014-05-06 15:20     ` Srinivas Pandruvada
2014-05-06 15:53       ` Srinivas Pandruvada
2014-05-07  7:16       ` Jean Delvare

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=536A22D2.5070104@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fenghua.yu@intel.com \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=srinivas.pandruvada@linux.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