On 5 March 2013 09:06, Mark Brown <[email protected]> wrote: > On Tue, Mar 05, 2013 at 08:53:47AM +0530, Sachin Kamat wrote: >> module_platform_driver_probe() eliminates the boilerplate and simplifies >> the code. > > Is there really any great reason to use this as opposed to > module_platform_driver()?
Since the init function returns platform_driver_probe() instead of platform_driver_register(), I have used module_platform_driver_probe() macro. >I know the existing code does this, it's not > clear to me that that's a good idea either. However, if your question is why return platform_driver_probe() at all instead of platform_driver_register() in the first place, then I am sorry I do not have much idea about it. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
