From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Lee Jones <lee.jones@linaro.org>, Simon <horms@verge.net.au>,
Magnus <magnus.damm@gmail.com>,
Linux-SH <linux-sh@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH] regulator: gpio: reborn necessary prop
Date: Thu, 13 Feb 2014 03:39:07 +0000 [thread overview]
Message-ID: <87iosjd6lj.wl%kuninori.morimoto.gx@gmail.com> (raw)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
934624d6e9f0b3d41557c4105c286e8daeaadb4e
(regulator: gpio-regulator: do not open-code counting and access of dt array elements)
removed struct property *prop from of_get_gpio_regulator_config()
but, it is still used on
0094050d783bbadffe83effef11a0bda901153ce
(regulator: gpio: add gpios-status for DT)
Compile will fail without this patch
gpio-regulator.c: In function 'of_get_gpio_regulator_config':
gpio-regulator.c:174:2: error: 'prop' undeclared (first use in this function)
gpio-regulator.c:174:2: note: each undeclared identifier is reported \
only once for each function it appears in
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
---
This is for latest mark-regulator/topic/gpio branch
drivers/regulator/gpio-regulator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/gpio-regulator.c b/drivers/regulator/gpio-regulator.c
index 9fd5561..20248c1 100644
--- a/drivers/regulator/gpio-regulator.c
+++ b/drivers/regulator/gpio-regulator.c
@@ -136,6 +136,7 @@ static struct gpio_regulator_config *
of_get_gpio_regulator_config(struct device *dev, struct device_node *np)
{
struct gpio_regulator_config *config;
+ struct property *prop;
const char *regtype;
int proplen, gpio, i;
int ret;
--
1.7.9.5
next reply other threads:[~2014-02-13 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 3:39 Kuninori Morimoto [this message]
2014-02-13 19:03 ` [PATCH] regulator: gpio: reborn necessary prop 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=87iosjd6lj.wl%kuninori.morimoto.gx@gmail.com \
--to=kuninori.morimoto.gx@gmail.com \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).