| 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, 10 Dec 2009 19:47:11 -0800 From: Greg KH <gregkh@...e.de> To: David Brownell <david-b@...bell.net> Cc: Jani Nikula <ext-jani.1.nikula@...ia.com>, dbrownell@...rs.sourceforge.net, linux-kernel@...r.kernel.org, dsilvers@...tec.co.uk, ben@...tec.co.uk, Artem.Bityutskiy@...ia.com, akpm@...ux-foundation.org Subject: Re: [PATCH 3/3] gpiolib: use chip->names for symlinks, always use gpioN for device names On Thu, Dec 10, 2009 at 07:39:30PM -0800, David Brownell wrote: > On Wednesday 09 December 2009, Jani Nikula wrote: > > While the device names are now unique again, collisions in chip->names > > will still prevent duplicates from being exported to sysfs. > > That's why I was never a real fan of chip->names... > > IMO a "good" solution in this space needs to accept that > those names are not going to be globally unique ... but > that they'll be unique within some context, of necessity. > > If Greg doesn't want to see those names under classes, > so be it ... but where should they then appear? As a sysfs file within the device directory called 'name'? Then just grep through the tree to find the right device, that also handles duplicates just fine, right? thanks, greg k-h -- 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