linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: foss <fabien.dessenne@foss.st.com>
To: <angkery@163.com>, <linus.walleij@linaro.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre TORGUE-SCND-02 <alexandre.torgue@foss.st.com>,
	<maz@kernel.org>,
	Etienne CARRIERE-SCND-01 <etienne.carriere@foss.st.com>,
	<geert+renesas@glider.be>, <matti.vaittinen@fi.rohmeurope.com>,
	<marex@denx.de>
Cc: <linux-gpio@vger.kernel.org>,
	"linux-stm32@st-md-mailman.stormreply.com" 
	<linux-stm32@st-md-mailman.stormreply.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<yangjunlin@yulong.com>
Subject: Re: [PATCH] pinctrl: stm32: add missing of_node_put
Date: Mon, 15 Feb 2021 14:56:56 +0100	[thread overview]
Message-ID: <6d7ad2ea-92dc-3caa-a931-2c932325a46b@foss.st.com> (raw)
In-Reply-To: <4a576fb8-682e-d1af-777d-436f9bc53794@foss.st.com>

Resending in plain-text format.


On 15/02/2021 2:26 pm, foss wrote:
>
> Hi Junlin
>
>
> Thank you for the patch!
>
>
> Fabien
>
>
>> From: Junlin Yang<yangjunlin@yulong.com>
>>
>> Fix OF node leaks by calling of_node_put in for_each_available_child_of_node when the cycle returns.
>>
>> Generated by: scripts/coccinelle/iterators/for_each_child.cocci
>>
>> Signed-off-by: Junlin Yang<yangjunlin@yulong.com>
>
> Acked-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
>
>
>> ---
>>   drivers/pinctrl/stm32/pinctrl-stm32.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c b/drivers/pinctrl/stm32/pinctrl-stm32.c
>> index 7d9bded..da72e3e 100644
>> --- a/drivers/pinctrl/stm32/pinctrl-stm32.c
>> +++ b/drivers/pinctrl/stm32/pinctrl-stm32.c
>> @@ -1542,8 +1542,10 @@ int stm32_pctl_probe(struct platform_device *pdev)
>>   		if (of_property_read_bool(child, "gpio-controller")) {
>>   			bank->rstc = of_reset_control_get_exclusive(child,
>>   								    NULL);
>> -			if (PTR_ERR(bank->rstc) == -EPROBE_DEFER)
>> +			if (PTR_ERR(bank->rstc) == -EPROBE_DEFER) {
>> +				of_node_put(child);
>>   				return -EPROBE_DEFER;
>> +			}
>>   
>>   			bank->clk = of_clk_get_by_name(child, NULL);
>>   			if (IS_ERR(bank->clk)) {
>> @@ -1551,6 +1553,7 @@ int stm32_pctl_probe(struct platform_device *pdev)
>>   					dev_err(dev,
>>   						"failed to get clk (%ld)\n",
>>   						PTR_ERR(bank->clk));
>> +				of_node_put(child);
>>   				return PTR_ERR(bank->clk);
>>   			}
>>   			i++;
>> --
>> 1.9.1
>>

       reply	other threads:[~2021-02-15 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4a576fb8-682e-d1af-777d-436f9bc53794@foss.st.com>
2021-02-15 13:56 ` foss [this message]
2021-02-15 10:36 [PATCH] pinctrl: stm32: add missing of_node_put angkery
2021-03-02  9:03 ` Linus Walleij

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=6d7ad2ea-92dc-3caa-a931-2c932325a46b@foss.st.com \
    --to=fabien.dessenne@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=angkery@163.com \
    --cc=etienne.carriere@foss.st.com \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@denx.de \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=maz@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=yangjunlin@yulong.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).