linux-kernel - [PATCH] drivers:regulator:change debug statement be consistent with the style of the rest.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 17 Apr 2011 08:53:57 +0800
From:	Wanlong Gao <wanlong.gao@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	linux-kernel@...r.kernel.org, trivial@...nel.org,
	lrg@...mlogic.co.uk
Subject: [PATCH] drivers:regulator:change debug statement be consistent with
 the style of the rest.



change the "mc13783_regulator_probe" string in the function 
"mc13783_regulator_probe"
to "__func__" for the debug statement be consistent with the style of 
the rest of
the file.

Signed-off-by: Wanlong Gao <wanlong.gao@...il.com>
Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

---
  drivers/regulator/mc13783-regulator.c |    2 +-
  1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/regulator/mc13783-regulator.c 
b/drivers/regulator/mc13783-regulator.c
index 23249cb..b8a00c7 100644
--- a/drivers/regulator/mc13783-regulator.c
+++ b/drivers/regulator/mc13783-regulator.c
@@ -341,7 +341,7 @@ static int __devinit mc13783_regulator_probe(struct 
platform_device *pdev)
         struct mc13783_regulator_init_data *init_data;
         int i, ret;

-       dev_dbg(&pdev->dev, "mc13783_regulator_probe id %d\n", pdev->id);
+       dev_dbg(&pdev->dev, "%s id %d\n", __func__, pdev->id);

         priv = kzalloc(sizeof(*priv) +
                         pdata->num_regulators * 
sizeof(priv->regulators[0]),
-- 
1.7.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/