From: Matthias Brugger <matthias.bgg@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
blogic@openwrt.org, arnd@arndb.de, henryc.chen@mediatek.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] soc: mediatek: PMIC wrap: Fix error handling
Date: Wed, 10 May 2017 12:43:43 +0200 [thread overview]
Message-ID: <106d786b-165c-ae5e-5180-3b8126d9e8bc@gmail.com> (raw)
In-Reply-To: <20170219131249.12010-1-christophe.jaillet@wanadoo.fr>
On 19/02/17 14:12, Christophe JAILLET wrote:
> According to error handling in this function, it is likely that going to
> 'err_out2' was expected here.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Applied to v4.12-next/soc
Sorry for the delay.
Matthias
> ---
> drivers/soc/mediatek/mtk-pmic-wrap.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> index a5f10936fb9c..285b434449a6 100644
> --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> @@ -1200,7 +1200,8 @@ static int pwrap_probe(struct platform_device *pdev)
>
> if (!(pwrap_readl(wrp, PWRAP_WACS2_RDATA) & PWRAP_STATE_INIT_DONE0)) {
> dev_dbg(wrp->dev, "initialization isn't finished\n");
> - return -ENODEV;
> + ret = -ENODEV;
> + goto err_out2;
> }
>
> /* Initialize watchdog, may not be done by the bootloader */
> @@ -1220,8 +1221,10 @@ static int pwrap_probe(struct platform_device *pdev)
> goto err_out2;
>
> wrp->regmap = devm_regmap_init(wrp->dev, NULL, wrp, &pwrap_regmap_config);
> - if (IS_ERR(wrp->regmap))
> - return PTR_ERR(wrp->regmap);
> + if (IS_ERR(wrp->regmap)) {
> + ret = PTR_ERR(wrp->regmap);
> + goto err_out2;
> + }
>
> ret = of_platform_populate(np, NULL, NULL, wrp->dev);
> if (ret) {
>
prev parent reply other threads:[~2017-05-10 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 13:12 Christophe JAILLET
2017-05-10 10:43 ` Matthias Brugger [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=106d786b-165c-ae5e-5180-3b8126d9e8bc@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=arnd@arndb.de \
--cc=blogic@openwrt.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=henryc.chen@mediatek.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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
all inboxes | Powered by JetHome®