From: <fabien.dessenne@foss.st.com>
To: 'Andy Shevchenko' <andriy.shevchenko@linux.intel.com>,
'Linus Walleij' <linus.walleij@linaro.org>
Cc: <linux-gpio@vger.kernel.org>, 'Stephen Rothwell' <sfr@canb.auug.org.au>
Subject: RE: [PATCH] pinctrl: stm32: Fix up errorpath after merge
Date: Fri, 6 May 2022 14:16:01 +0200 [thread overview]
Message-ID: <028501d86143$10368060$30a38120$@foss.st.com> (raw)
In-Reply-To: <YnQSrDfdjFRnMz+k@smile.fi.intel.com>
Hi Andy & Linus,
I confirm that the merge fix is OK.
Fabien
ST Restricted
> -----Original Message-----
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Sent: jeudi 5 mai 2022 20:09
> To: Linus Walleij <linus.walleij@linaro.org>
> Cc: linux-gpio@vger.kernel.org; Stephen Rothwell <sfr@canb.auug.org.au>;
> Fabien Dessenne <fabien.dessenne@foss.st.com>
> Subject: Re: [PATCH] pinctrl: stm32: Fix up errorpath after merge
>
> On Thu, May 05, 2022 at 04:28:37PM +0200, Linus Walleij wrote:
> > When merging the for_each_gpiochip_node() changes, I made some
> > mistakes by not disabling the clocks on the errorpath, fix it up.
>
> At least this is what I found,
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> but I might have missed something, it would be nice if ST guys can look
into this
> as well.
>
> > Fixes: a0912083086d ("Merge tag 'intel-gpio-v5.19-1' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel
> > into devel")
> > Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> > Cc: Fabien Dessenne <fabien.dessenne@foss.st.com>
> > Reported-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > drivers/pinctrl/stm32/pinctrl-stm32.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c
> > b/drivers/pinctrl/stm32/pinctrl-stm32.c
> > index 0f7d608151ff..88da8ac0b252 100644
> > --- a/drivers/pinctrl/stm32/pinctrl-stm32.c
> > +++ b/drivers/pinctrl/stm32/pinctrl-stm32.c
> > @@ -1614,6 +1614,10 @@ int stm32_pctl_probe(struct platform_device
> *pdev)
> > ret = stm32_gpiolib_register_bank(pctl, child);
> > if (ret) {
> > fwnode_handle_put(child);
> > +
> > + for (i = 0; i < pctl->nbanks; i++)
> > + clk_disable_unprepare(pctl->banks[i].clk);
> > +
> > return ret;
> > }
> >
> > --
> > 2.35.1
> >
>
> --
> With Best Regards,
> Andy Shevchenko
>
prev parent reply other threads:[~2022-05-06 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 14:28 [PATCH] pinctrl: stm32: Fix up errorpath after merge Linus Walleij
2022-05-05 18:08 ` Andy Shevchenko
2022-05-06 12:16 ` fabien.dessenne [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='028501d86143$10368060$30a38120$@foss.st.com' \
--to=fabien.dessenne@foss.st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).