> >> On Mon, Feb 10, 2014 at 4:38 PM, Jean Delvare <jdelv...@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, why don't you try to work _with_ the current ruling and the Maintainers to see what others have done to solve the problem. I highly doubt you are the first/only developer who has had this issue. Do: `git grep "\-hwmon"` ... and have a good look around for an accepted solution. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
