From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Andi Kleen <andi@firstfloor.org>, rafael.j.wysocki@intel.com
Cc: dirk.j.brandewie@intel.com, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] intel_pstate: Turn per cpu printk into pr_debug
Date: Wed, 27 Aug 2014 10:27:58 -0700 [thread overview]
Message-ID: <53FE151E.6010708@intel.com> (raw)
In-Reply-To: <1409159828-16168-1-git-send-email-andi@firstfloor.org>
On 08/27/2014 10:17 AM, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> On larger systems intel_pstate currently spams the boot up
> log with its "Intel pstate controlling ..." message for each CPU.
> It's the only subsystem that prints a message for each
> CPU.
>
> Turn the message into a pr_debug.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
> ---
> drivers/cpufreq/intel_pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index c5eac94..17be734 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -688,7 +688,7 @@ static int intel_pstate_init_cpu(unsigned int cpunum)
>
> add_timer_on(&cpu->timer, cpunum);
>
> - pr_info("Intel pstate controlling: cpu %d\n", cpunum);
> + pr_debug("Intel pstate controlling: cpu %d\n", cpunum);
>
> return 0;
> }
>
next prev parent reply other threads:[~2014-08-27 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 17:17 [PATCH] intel_pstate: Turn per cpu printk into pr_debug Andi Kleen
2014-08-27 17:27 ` Dirk Brandewie [this message]
2014-08-27 23:43 ` Rafael J. Wysocki
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=53FE151E.6010708@intel.com \
--to=dirk.brandewie@gmail.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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