| 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: Sun, 13 Mar 2011 11:41:07 +0100 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Greg KH <greg@...ah.com>, linux-usb@...r.kernel.org Cc: Andy Green <andy@...mcat.com>, linux-kernel@...r.kernel.org, patches@...aro.org, Andy Green <andy.green@...aro.org> Subject: Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform_data attach api On Sunday, March 13, 2011, Greg KH wrote: > On Sat, Mar 12, 2011 at 10:32:27PM +0000, Andy Green wrote: > > This introduces a platform API so busses can allow platform_data to > > be attached to any struct device they create from probing in one step. > > > > The function checks through the async platform_data map if one was > > previously registered, and checks the device's device path for itself > > and its parents against the mapped device path names. > > > > If it sees a match, it attaches the associated platform_data and sets > > that map entry's device_path to NULL so no further time is spent trying > > to match it. > > This _really_ should just use the device tree stuff, that is what it is > for, please don't duplicate it here in a not-as-flexible way. I agree. @Andy: If it doesn't work for you for some reason, please let us know the usage case that is not covered (in detail). Thanks, Rafael -- 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