| 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, 11 Mar 2009 10:35:29 -0600 From: Grant Likely <grant.likely@...retlab.ca> To: Greg KH <gregkh@...e.de> Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org Subject: Re: [RFC] drivers/base: Add bus_register_notifier_alldev() variant On Wed, Mar 11, 2009 at 10:26 AM, Greg KH <gregkh@...e.de> wrote: > On Fri, Mar 06, 2009 at 09:10:19AM -0700, Grant Likely wrote: >> From: Grant Likely <grant.likely@...retlab.ca> >> >> bus_register_notifier_alldev() is a variation on bus_register_notifier() >> which also triggers the notifier callback for devices already on the bus >> and already bound to drivers. >> >> This function is useful for the case where a driver needs to get a >> reference to a struct device other than the one it is bound to and >> it is not known if the device will be bound before or after this >> function is called. For example, an Ethernet device connected to >> a PHY that is probed separately. > > Can't you just walk the list of all devices already on the bus to get > "notified" of them, and then register your notifier handler as well (or > register it first, and then walk the list, which is pretty much what > your patch does)? Yes, and I originally did, but it looks to me like a useful common pattern that is less error prone than open coding it. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- 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