| 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: Wed, 21 Nov 2012 06:52:39 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Grant Likely <grant.likely@...retlab.ca> Cc: linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org> Subject: Re: [RFC] driver-core: Remove dummy 'platform_bus' On Wed, Nov 21, 2012 at 02:44:31PM +0000, Grant Likely wrote: > The "platform_bus" (note: not platform_bus_type) only exists as an empty > directory to put platform devices into. However, it really doesn't make > sense to segregate all the platform devices into a sub directory when > typically they are memory mapped devices that doen't go through any > particular bus. Particularly on embedded type platforms the platform_bus > directory doesn't add anything. > > However, this will probably just end up breaking some userspace that > depends on the /sys/devices/platform/ path to be present (no matter how > much we protest that userspace must not depend on paths in sysfs). So > while I'm seriously proposing this change, it may just be unacceptable > ABI breakage If the devices don't show up under platform/ where are they going to be at now, virtual/ ? That doesn't sound like a good plan, they should be somewhere "useful". And yes, odds are this will break userspace, but we might not know until we try it, have you tried it on different distros to see what happens? 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