[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7618517.DFSqTW80gq@vostro.rjw.lan>
Date: Wed, 31 Jul 2013 23:10:51 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Viresh Kumar <viresh.kumar@...aro.org>,
linaro-kernel@...ts.linaro.org, patches@...aro.org,
cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd.bergmann@...aro.org,
Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH 14/15] cpufreq: Tegra: initialize .owner field with THIS_MODULE
On Wednesday, July 31, 2013 01:13:09 PM Stephen Warren wrote:
> On 07/31/2013 08:19 AM, Viresh Kumar 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 this driver, lets initialize it with
> > THIS_MODULE.
>
> Acked-by: Stephen Warren <swarren@...dia.com>
>
> I assume this is all part of a series you'll take through the cpufreq tree.
I'm going to apply this series eventually, but I'd like some ACKs to accumulate
before doing that.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists