[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190621101043.10549-1-pawel.mikolaj.chmiel@gmail.com>
Date: Fri, 21 Jun 2019 12:10:43 +0200
From: Paweł Chmiel <pawel.mikolaj.chmiel@...il.com>
To: kgene@...nel.org
Cc: krzk@...nel.org, rjw@...ysocki.net, viresh.kumar@...aro.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [RESEND,v2] cpufreq: s5pv210: Don't flood kernel log after cpufreq change
This commit replaces printk with pr_debug, so we don't flood kernel log.
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@...il.com>
Acked-by: Krzysztof Kozlowski <krzk@...nel.org>
---
Changes from v1:
- Added Acked-by
---
drivers/cpufreq/s5pv210-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/s5pv210-cpufreq.c b/drivers/cpufreq/s5pv210-cpufreq.c
index 5b4289460bc9..c7b7d1e65b08 100644
--- a/drivers/cpufreq/s5pv210-cpufreq.c
+++ b/drivers/cpufreq/s5pv210-cpufreq.c
@@ -481,7 +481,7 @@ static int s5pv210_target(struct cpufreq_policy *policy, unsigned int index)
arm_volt, arm_volt_max);
}
- printk(KERN_DEBUG "Perf changed[L%d]\n", index);
+ pr_debug("Perf changed[L%d]\n", index);
exit:
mutex_unlock(&set_freq_lock);
--
2.17.1
Powered by blists - more mailing lists