lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 11 Feb 2014 03:13:37 +0000 From: Laszlo Papp <lpapp@....org> To: Jean Delvare <jdelvare@...e.de> Cc: Lee Jones <lee.jones@...aro.org>, LKML <linux-kernel@...r.kernel.org>, Guenter Roeck <linux@...ck-us.net>, lm-sensors@...sensors.org Subject: Re: [lm-sensors] [PATCH] hwmon: (max6650) Rename the device ids to contain the hwmon suffix On Mon, Feb 10, 2014 at 4:38 PM, Jean Delvare <jdelvare@...e.de> wrote: > Additionally, dashes are explicitly forbidden in hwmon > device names. Also, where is that documented? I do not think you can make such a decision, and you will realize that once you begin to think a bit out of the box and look around. See how other children are managed for MFD devices. "driver-subsystem" is a pretty common a schema. I do not really see any point in forbidding dashes currently. Please do elaborate about the reasons, and the fact that why it is undocuemented. Also, I currently do not understand what you are suggesting: just leave this technically unreasonable situation as is for compatibility reasons? There is no better support in place for appending further alternative names? In any case, at the very least, I hope the lesson is learnt for the future from this past mistake. If a chip is MFD'ish, a subdevice driver should not ever be added with such an id. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists