mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Laszlo Papp <lpapp@kde.org>
Cc: Jean Delvare <jdelvare@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] hwmon: (max6650) Rename the device ids to contain the hwmon suffix
Date: Tue, 11 Feb 2014 09:47:26 +0000	[thread overview]
Message-ID: <20140211094726.GH32042@lee--X1> (raw)
In-Reply-To: <CAOMwXhPfmXDKcov_+HHDTCaieGDiMEi+6CV_OnYDM3c8+S+bfA@mail.gmail.com>

> >> >> On Mon, Feb 10, 2014 at 4:38 PM, Jean Delvare <jdelvare@suse.de> wrote:
> >> >> > Additionally, dashes are explicitly forbidden in hwmon
> >> >> > device names.
> >> >>
> >> >> Also, where is that documented?
> >> >
> >> > In Documentation/hwmon/sysfs-interface:
> >> >
> >> > *********************
> >> > * Global attributes *
> >> > *********************
> >> >
> >> > name            The chip name.
> >> >                 This should be a short, lowercase string, not containing
> >> >                 spaces nor dashes, representing the chip name. This is
> >> >                 the only mandatory attribute.
> >> >                 I2C devices get this attribute created automatically.
> >> >                 RO
> >>
> >> Time to revisit this decision....
> >>
> >> So, based on the fact that children device names usually contain
> >> dashes, I do not understand why hwmon would be any special in this
> >> regard. It is possible that the hwmon developers have not faced much
> >> MFD situation before, and so, this was not considered to be handled
> >> like in other subsystems.
> >>
> >> I am proposing to change this "rule"...  Any objection?
> >
> > Prior to proposing such an invasive change which is highly likely to
> > come up against heavy opposition,
> 
> It is possible that someone does not understand why you think it may
> be invasive, right? Could you please explain the reason for that?

The reason is a good one. In the kernel we make every attempt not to
break userspace. By that I mean _any_ userspace application. Userspace
applications which interface with the kernel can do so via a variety of
methods. One of those is Sysfs, where this name you are attempting to
change appears. The userspace applications already mentioned parse for
these devices, regex:ing for '-' separators. If you add an additional
'-' separator there is a chance that these applications will get
confused and break without warning. 

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2014-02-11  9:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 15:25 Laszlo Papp
2014-02-10 16:08 ` Lee Jones
2014-02-10 16:38   ` [lm-sensors] " Jean Delvare
2014-02-10 16:53     ` linux
2014-02-10 18:59       ` Laszlo Papp
2014-02-10 23:10         ` Guenter Roeck
2014-02-11  3:23           ` Laszlo Papp
2014-02-11  3:35             ` Laszlo Papp
2014-02-10 16:58     ` Lee Jones
2014-02-10 17:43       ` Jean Delvare
2014-02-10 18:01         ` Lee Jones
2014-02-10 18:15           ` [lm-sensors] " Jean Delvare
2014-02-10 18:24             ` Lee Jones
2014-02-10 18:27         ` Laszlo Papp
2014-02-10 18:55           ` [lm-sensors] " Jean Delvare
2014-02-10 17:06     ` Laszlo Papp
2014-02-10 17:09       ` Laszlo Papp
2014-02-11  3:13     ` Laszlo Papp
2014-02-11  7:50       ` Jean Delvare
2014-02-11  8:19         ` Laszlo Papp
2014-02-11  8:28         ` Laszlo Papp
2014-02-11  8:49           ` Jean Delvare
2014-02-11  9:08             ` Laszlo Papp
2014-02-11  9:57               ` Lee Jones
2014-02-11 15:15                 ` Laszlo Papp
2014-02-11  8:50           ` Lee Jones
2014-02-11  8:58             ` Laszlo Papp
2014-02-11  9:14               ` Laszlo Papp
2014-02-11  9:47               ` Lee Jones [this message]
2014-02-11  9:50                 ` Laszlo Papp
2014-02-11 10:22             ` Laszlo Papp
2014-02-11 11:09               ` Laszlo Papp

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=20140211094726.GH32042@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=lpapp@kde.org \
    /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

all inboxes | Powered by JetHome®