summaryrefslogtreecommitdiffstats
path: root/drivers/regulator
diff options
context:
space:
mode:
authorMark Brown <broonie@opensource.wolfsonmicro.com>2012-02-09 13:08:39 +0000
committerMark Brown <broonie@opensource.wolfsonmicro.com>2012-02-09 16:22:06 +0000
commit43f674a322aa8a3404df5785f84dc1351a5d84b6 (patch)
treedf913893b03ed8594278b378bd05bca9d0bf8f6e /drivers/regulator
parent49e226323d462785582750d9f38acca5ffa5dd48 (diff)
downloadlinux-43f674a322aa8a3404df5785f84dc1351a5d84b6.tar.bz2
regulator: Don't add the function name to pr_fmt
Liam pointed out via IM that since we now use the pure function name for all regulator logging a lot of the messages such as those logging the constraints are getting a bit noisy due to the implementation detail that is the function name: print_constraints: VDDARM: 1000 <--> 1300 mV at 1300 mV at 0 mA In discussion it seemed like the best thing was to just drop the pr_fmt and clarify individual log messages where there is an issue otherwise we get into silly things like renaming the functions to suit the logging. This is mostly an issue as we have a moderate amount of non-error logging in the boot sequence to aid debug if something goes wrong since regulator misconfiguration can kill the system pretty quickly. Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> Acked-by: Liam Girdwood <lrg@ti.com>
Diffstat (limited to 'drivers/regulator')
-rw-r--r--drivers/regulator/core.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index daba2f60f7d9..e3271daa3ab9 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -13,8 +13,6 @@
*
*/
-#define pr_fmt(fmt) "%s: " fmt, __func__
-
#include <linux/kernel.h>
#include <linux/init.h>
#include <linux/debugfs.h>