On Tue, Mar 01, 2011 at 10:32:00PM +0100, Thomas Renninger wrote: > On Tuesday 01 March 2011 17:41:10 Jiri Slaby wrote: > > cpufreq_register_driver sets cpufreq_driver to a structure owned (and > > placed) in the caller's memory. If cpufreq policy fails in its ->init > > function, sysdev_driver_register returns nonzero in > > cpufreq_register_driver. Now, cpufreq_register_driver returns an error > > without setting cpufreq_driver back to NULL. > > > > Usually cpufreq policy modules are unloaded because they propagate the > > error to the module init function and return that. > > Looks pretty sane and makes the code much nicer. > > Will you pick it up Dave? yep, got it. thanks, Dave -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
