From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Ian Lartey <ian@opensource.wolfsonmicro.com>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH] regulator: (wm831x-dcdc) Remove unused variables
Date: Wed, 25 May 2011 23:58:11 -0700 [thread overview]
Message-ID: <1306393091-6036-1-git-send-email-linux@roeck-us.net> (raw)
Remove unused variable wm831x from functions wm831x_buckv_remove() and
wm831x_buckp_remove().
This commit fixes the following build warnings:
drivers/regulator/wm831x-dcdc.c: In function wm831x_buckv_remove:
rivers/regulator/wm831x-dcdc.c:603: warning: unused variable wm831x
drivers/regulator/wm831x-dcdc.c: In function wm831x_buckp_remove:
drivers/regulator/wm831x-dcdc.c:779: warning: unused variable wm831x
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
drivers/regulator/wm831x-dcdc.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/wm831x-dcdc.c b/drivers/regulator/wm831x-dcdc.c
index e93453b..a0982e8 100644
--- a/drivers/regulator/wm831x-dcdc.c
+++ b/drivers/regulator/wm831x-dcdc.c
@@ -600,7 +600,6 @@ err:
static __devexit int wm831x_buckv_remove(struct platform_device *pdev)
{
struct wm831x_dcdc *dcdc = platform_get_drvdata(pdev);
- struct wm831x *wm831x = dcdc->wm831x;
platform_set_drvdata(pdev, NULL);
@@ -776,7 +775,6 @@ err:
static __devexit int wm831x_buckp_remove(struct platform_device *pdev)
{
struct wm831x_dcdc *dcdc = platform_get_drvdata(pdev);
- struct wm831x *wm831x = dcdc->wm831x;
platform_set_drvdata(pdev, NULL);
--
1.7.1
next reply other threads:[~2011-05-26 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 6:58 Guenter Roeck [this message]
2011-05-26 8:18 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306393091-6036-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=ian@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®