From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 2/2] regulator: gpio: Warn if an invalid regulator-type is supplied
Date: Thu, 05 Dec 2013 21:10:31 +0100 [thread overview]
Message-ID: <66015321.Q31GikVXiU@avalon> (raw)
In-Reply-To: <1386270722-13962-2-git-send-email-broonie@kernel.org>
Hi Mark,
Thank you for the patch.
On Thursday 05 December 2013 19:12:02 Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> Reported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Mark Brown <broonie@linaro.org>
I believe you could squash this patch with the one you've previously posted
that makes the property optional. For the result,
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/regulator/gpio-regulator.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/regulator/gpio-regulator.c
> b/drivers/regulator/gpio-regulator.c index 13ec94d984ca..c0a1d00b78c9
> 100644
> --- a/drivers/regulator/gpio-regulator.c
> +++ b/drivers/regulator/gpio-regulator.c
> @@ -210,6 +210,9 @@ of_get_gpio_regulator_config(struct device *dev, struct
> device_node *np) config->type = REGULATOR_VOLTAGE;
> else if (!strncmp("current", regtype, 7))
> config->type = REGULATOR_CURRENT;
> + else
> + dev_warn(dev, "Unknown regulator-type '%s'\n",
> + regtype);
> }
>
> return config;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-12-05 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 19:12 [PATCH 1/2] regulator: gpio: Document regulator-type property Mark Brown
2013-12-05 19:12 ` [PATCH 2/2] regulator: gpio: Warn if an invalid regulator-type is supplied Mark Brown
2013-12-05 20:10 ` Laurent Pinchart [this message]
2013-12-05 20:08 ` [PATCH 1/2] regulator: gpio: Document regulator-type property Laurent Pinchart
2013-12-05 20:42 ` 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=66015321.Q31GikVXiU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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