summaryrefslogtreecommitdiffstats
path: root/drivers/regulator
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-05-17 15:15:30 +0300
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-05-23 08:22:20 +0300
commit56e46742e846e4de167dde0e1e1071ace1c882a5 (patch)
treeffed000ab5bb33d482878bd72420474bdab1eec4 /drivers/regulator
parentbdc1a1b6100c78a6002b1761ebe36d5fe8f8585b (diff)
downloadop-kernel-dev-56e46742e846e4de167dde0e1e1071ace1c882a5.zip
op-kernel-dev-56e46742e846e4de167dde0e1e1071ace1c882a5.tar.gz
UBIFS: switch to dynamic printks
Switch to debugging using dynamic printk (pr_debug()). There is no good reason to carry custom debugging prints if there is so cool and powerful generic dynamic printk infrastructure, see Documentation/dynamic-debug-howto.txt. With dynamic printks we can switch on/of individual prints, per-file, per-function and per format messages. This means that instead of doing old-fashioned echo 1 > /sys/module/ubifs/parameters/debug_msgs to enable general messages, we can do: echo 'format "UBIFS DBG gen" +ptlf' > control to enable general messages and additionally ask the dynamic printk infrastructure to print process ID, line number and function name. So there is no reason to keep UBIFS-specific crud if there is more powerful generic thing. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud