On Wed, Mar 11, 2009 at 10:26 AM, Greg KH <gre...@suse.de> wrote: > On Fri, Mar 06, 2009 at 09:10:19AM -0700, Grant Likely wrote: >> From: Grant Likely <grant.lik...@secretlab.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. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev