From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: viresh kumar <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix problem with cpufreq_pndemand or cpufreq_conservative
Date: Sat, 29 Dec 2012 00:01:16 +0100 [thread overview]
Message-ID: <3226192.H2BxHSuKio@vostro.rjw.lan> (raw)
In-Reply-To: <50DE1A74.4040607@lwfinger.net>
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 cpufreq_governor is created. It seems that kmake is smart enough to create
> a separate module whenever more than one module includes the same object file.
> As drivers/cpufreq/cpufreq_governor.c contains no MODULE directives, the
> resulting module has no license specified, which results in logging of a "module
> license 'unspecified' taints kernel". In addition, a number of globals are
> exported GPL only, and are therefore not available.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> ---
>
> This particular patch is the simplest possible; however, it hides the intent. I
> have prepared the longer version that makes the reason clearer by adding a new
> configuration variable that is dependent on the other two, and rearranges
> drivers/cpufreq/Makefile. That version could be submitted if that is what is
> desired.
Yes, please.
> The changes to cpufreq_governor.c are the same as in this version.
I wonder if that's avoidable? The intention is not to create an additional
module, clearly.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-12-28 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 22:17 Larry Finger
2012-12-28 23:01 ` Rafael J. Wysocki [this message]
2012-12-28 23:45 ` Larry Finger
2012-12-29 0:33 ` Fabio Baltieri
2012-12-29 0:53 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3226192.H2BxHSuKio@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Larry.Finger@lwfinger.net \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®