On 31 July 2013 19:49, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> CPUFreq core does following at multiple places:
> module_{get|put}(cpufreq_driver->owner)).
>
> This is done to make sure module doesn't get unloaded if it is currently in use.
> This will work only if the .owner field of cpufreq driver is initialized with a
> valid pointer.
>
> This field wasn't initialized for many cpufreq driver, lets initialize it with
> THIS_MODULE.
You can drop this patchset now as .owner field is removed in the latest
patchset from me which is posted today:
"[PATCH 00/10] CPUFreq: Fixes & Cleanups for 3.12"
--
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
