On Thu, 30 Jun 2011, Kevin Hilman wrote: > Another curiosity is that, contrary to the above documentation, there is > no usage_count increment before the bus/driver ->remove() (although > there is a _get_sync/_put_sync around the sysfs_remove and notifier just > before the bus/driver->remove().
I hadn't noticed that. There may be a reason for using get_sync instead of get_noresume, but it isn't explained anywhere. And it certainly looks like a mistake for the put_sync to occur before the ->remove() call instead of after. This needs to be fixed. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
