From: S Twiss <stwiss.opensource@diasemi.com>
To: LINUXKERNEL <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: David Dajun Chen <david.chen@diasemi.com>,
Support Opensource <support.opensource@diasemi.com>
Subject: [PATCH V1] regulators: da9062: Remove unused variable build warning
Date: Mon, 1 Jun 2015 14:00:20 +0100 [thread overview]
Message-ID: <201506011306.t51D6Ski017669@swsrvapps-01.diasemi.com> (raw)
From: S Twiss <stwiss.opensource@diasemi.com>
Remove the unused variable build warning for reg_matches that appears
during the compilation of the DA9062 regulator driver.
da9062-regulator.c: In function da9062_regulator_probe:
da9062-regulator.c:727:29: warning: unused variable reg_matches
Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
---
This patch applies against linux-next and next-20150528
drivers/regulator/da9062-regulator.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/regulator/da9062-regulator.c b/drivers/regulator/da9062-regulator.c
index e572a65..dd76da0 100644
--- a/drivers/regulator/da9062-regulator.c
+++ b/drivers/regulator/da9062-regulator.c
@@ -724,7 +724,6 @@ ldo_lim_error:
static int da9062_regulator_probe(struct platform_device *pdev)
{
struct da9062 *chip = dev_get_drvdata(pdev->dev.parent);
- struct of_regulator_match *reg_matches = NULL;
struct da9062_regulators *regulators;
struct da9062_regulator *regl;
struct regulator_config config = { };
--
end-of-patch for PATCH V1
next reply other threads:[~2015-06-01 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:00 S Twiss [this message]
2015-06-02 11:11 ` [PATCH V1] regulators: da9062: Remove unused variable build warning Mark Brown
2015-06-02 13:02 ` Opensource [Steve Twiss]
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=201506011306.t51D6Ski017669@swsrvapps-01.diasemi.com \
--to=stwiss.opensource@diasemi.com \
--cc=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.