From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: max14577: Fix invalid return value on DT parse success
Date: Fri, 21 Feb 2014 12:14:21 +0100 [thread overview]
Message-ID: <1392981261.19813.6.camel@AMDC1943> (raw)
In-Reply-To: <CAK9yfHyihSUdQFjKVZ1-c9iq4NKDWymbQKFgeBDMd-QWNYR61w@mail.gmail.com>
On Fri, 2014-02-21 at 16:25 +0530, Sachin Kamat wrote:
> On 21 February 2014 16:12, Krzysztof Kozlowski <k.kozlowski@samsung.com> wrote:
> > On Fri, 2014-02-21 at 15:54 +0530, Sachin Kamat wrote:
> >> Hi Krzysztof,
> >>
> >> On 20 February 2014 20:49, Krzysztof Kozlowski <k.kozlowski@samsung.com> wrote:
> >> > This fixes bug introduced in 667a6b7a (regulator: max14577: Add missing
> >> > of_node_put). The DTS parsing function returned number of matched
> >> > regulators as success status which then was compared against 0 in probe.
> >> >
> >> > Result was a probe fail after successful parsing the DTS:
> >> > max14577-regulator: probe of max14577-regulator failed with error 2
> >> >
> >> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> >> > ---
> >> > drivers/regulator/max14577.c | 4 +++-
> >> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >> >
> >> > diff --git a/drivers/regulator/max14577.c b/drivers/regulator/max14577.c
> >> > index 186df8785a91..6ba11a8dd23d 100644
> >> > --- a/drivers/regulator/max14577.c
> >> > +++ b/drivers/regulator/max14577.c
> >> > @@ -168,11 +168,13 @@ static int max14577_regulator_dt_parse_pdata(struct platform_device *pdev)
> >> > MAX14577_REG_MAX);
> >> > if (ret < 0) {
> >> > dev_err(&pdev->dev, "Error parsing regulator init data: %d\n", ret);
> >> > + of_node_put(np);
> >> > + return ret;
> >> > }
> >> >
> >> > of_node_put(np);
> >> >
> >> > - return ret;
> >> > + return 0;
> >> > }
> >>
> >> Instead of so many changes here, you could simply make the following change
> >> in the max14577_regulator_probe function.
> >>
> >> ret = max14577_regulator_dt_parse_pdata(pdev);
> >> if (ret < 0)
> >> return ret;
> >
> > That still wouldn't be sufficient because later in probe() the 'ret' is
> > not reassigned (if devm_regulator_register succeeds) and it is directly
> > returned at the probe() end. So still the number of matched regulators
> > would be returned as probe result.
>
> Ah, you are right. In that case how about the following:
>
> - if (ret < 0) {
> + if (ret < 0)
> dev_err(&pdev->dev, "Error parsing regulator init data: %d\n", ret);
> - }
> + else
> + ret = 0;
>
> I am just trying to see if we can avoid any code duplication.
Looks good. Thanks for idea, I'll send v2.
Best regards,
Krzysztof
prev parent reply other threads:[~2014-02-21 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 15:19 [PATCH] regulator: max14577: Fix invalid return value on DT parse success Krzysztof Kozlowski
2014-02-21 10:24 ` Sachin Kamat
2014-02-21 10:42 ` Krzysztof Kozlowski
2014-02-21 10:55 ` Sachin Kamat
2014-02-21 11:14 ` Krzysztof Kozlowski [this message]
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=1392981261.19813.6.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.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