regulator: core: Print at debug level on debugfs creation failure
authorStephen Boyd <sboyd@codeaurora.org>
Tue, 2 Jun 2015 01:47:55 +0000 (18:47 -0700)
committerMark Brown <broonie@kernel.org>
Fri, 14 Aug 2015 19:25:50 +0000 (20:25 +0100)
commitad3a942bd22fd40a0f4ddaf2759946ce945662af
tree45de74fccfc531ebc50a39ece930a27e048bec72
parent1635e88885a8e16dec21206c981421f1f3c3b1df
regulator: core: Print at debug level on debugfs creation failure

Failure to create a debugfs node is not an error, but we print a
warning upon failure to create the node. Downgrade this to a
debug printk so that we're quiet here. This allows multiple
drivers to request a CPU's regulator so that CPUfreq and AVSish
drivers can coexist.

The downside of this approach is that whoever gets to debugfs first
the others who come later to not have any debugfs attributes associated
with them.

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
drivers/regulator/core.c