| 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: Thu, 25 Jun 2009 14:16:25 +0100 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Jonathan Cameron <Jonathan.Cameron@...il.com> Cc: Liam Girdwood <lrg@...mlogic.co.uk>, linux-kernel@...r.kernel.org, Mike Rapoport <mike@...pulab.co.il> Subject: Re: [PATCH] regulator: Allow consumer supplies to be set up with dev_name() On Thu, Jun 25, 2009 at 01:11:46PM +0000, Jonathan Cameron wrote: > I just wonder if we need to suggest subsystem maintainers make sure that > their > device names are suitably unique and identifiable? For example, i2c device > tend to have names like 0-0032. Perhaps we need something to identify > that they > are indeed i2c devices? Either that or if it becomes a problem we add the ability to match on bus type as well - since bus type already exists it'd probably be better to go down that road rather than cause userspace-visible changes. I've not looked in sufficient detail to confirm that this would cover everything but I believe it should. > For that matter, is there anything other than blind luck preventing two > regulator > consumers having the same dev_name? Due to sysfs requirements I think we should be safe with the addition of bus type matching but like I say I may be missing something. -- 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