On Wed, 2012-10-17 at 11:25 +0530, Viresh Kumar wrote:
On 17 October 2012 11:09, Joe Perches joe@perches.com wrote:
On Wed, 2012-10-17 at 10:50 +0530, Viresh Kumar wrote:
With debug options on, it is difficult to locate cpufreq core's debug prints.
[]
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
[]
@@ -15,6 +15,8 @@ +#define pr_fmt(fmt) "cpufreq: " fmt
[]
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
Sorry, i am not sure how KBUILD_MODNAME is compiled by kernel.
KBUILD_MODNAME is a #define that is set by scripts/Makefile.lib.
So, if i try KBUILD_MODNAME with my patch i get prints as:
KBUILD_MODNAME: <print - text>
I believe you are quoting KBUILD_MODNAME
try
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
This should create prefixes like "cpufreq: " and "cpufreq_performance: "