On 12/28/2012 06:33 PM, Fabio Baltieri wrote:
On Fri, Dec 28, 2012 at 05:45:54PM -0600, Larry Finger wrote:
I wonder if that's avoidable? The intention is not to create an additional
module, clearly.
It appears not to be possible. I don't know enough about to kmake to
understand why it is for
On Fri, Dec 28, 2012 at 05:45:54PM -0600, Larry Finger wrote:
> >I wonder if that's avoidable? The intention is not to create an additional
> >module, clearly.
>
> It appears not to be possible. I don't know enough about to kmake to
> understand why it is forcing a new module. Perhaps some expert
On 12/28/2012 05:01 PM, Rafael J. Wysocki wrote:
On Friday, December 28, 2012 04:17:24 PM Larry Finger wrote:
Since commit 2aacdff entitled "cpufreq: Move common part from governors to
separate file", whenever the drivers that depend on this new file
(cpufreq_ondemand or cpufreq_conservative) ar
On Friday, December 28, 2012 04:17:24 PM Larry Finger wrote:
> Since commit 2aacdff entitled "cpufreq: Move common part from governors to
> separate file", whenever the drivers that depend on this new file
> (cpufreq_ondemand or cpufreq_conservative) are built as modules, a new module
> named cp
4 matches
Mail list logo