On 17 October 2012 11:09, Joe Perches <joe@xxxxxxxxxxx> 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 > > I'd prefer that > > #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt > > be used for all of these. Hi Joe, Sorry, i am not sure how KBUILD_MODNAME is compiled by kernel. If i am not wrong KBUILD_MODNAME would work only for drivers that can be added as module? If so, then it may not apply here, as most of the stuff i have updated doesn't call module_init(). So, if i try KBUILD_MODNAME with my patch i get prints as: KBUILD_MODNAME: <print - text> -- viresh -- 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
