From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: arc: Fix a potential memory leak if an optional regulator is deferred
Date: Fri, 16 Mar 2018 21:51:21 +0100 [thread overview]
Message-ID: <89a63178-a08a-5023-a045-018b4d7b11bc@wanadoo.fr> (raw)
In-Reply-To: <20180316.152712.1584177628223195375.davem@davemloft.net>
Le 16/03/2018 à 20:27, David Miller a écrit :
> From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> Date: Wed, 14 Mar 2018 22:09:34 +0100
>
>> diff --git a/drivers/net/ethernet/arc/emac_rockchip.c b/drivers/net/ethernet/arc/emac_rockchip.c
>> index 16f9bee992fe..8ee9dfd0e363 100644
>> --- a/drivers/net/ethernet/arc/emac_rockchip.c
>> +++ b/drivers/net/ethernet/arc/emac_rockchip.c
>> @@ -169,8 +169,10 @@ static int emac_rockchip_probe(struct platform_device *pdev)
>> /* Optional regulator for PHY */
>> priv->regulator = devm_regulator_get_optional(dev, "phy");
>> if (IS_ERR(priv->regulator)) {
>> - if (PTR_ERR(priv->regulator) == -EPROBE_DEFER)
>> - return -EPROBE_DEFER;
>> + if (PTR_ERR(priv->regulator) == -EPROBE_DEFER) {
>> + ret = -EPROBE_DEFER;
>> + goto out_clk_disable;
>> + }
> Please build test your changes.
>
> There is no 'ret' variable in this function, perhaps you meant 'err'.
>
Yes, obviously, this is 'err'.
I apologize. I usually build-test all my patches before submission.
This one seems to have gone out of my normal process.
Can you fix it yourself or do you want me to re-submit?
CJ
next prev parent reply other threads:[~2018-03-16 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 21:09 Christophe JAILLET
2018-03-16 19:27 ` David Miller
2018-03-16 20:51 ` Christophe JAILLET [this message]
2018-03-16 20:52 ` Christophe JAILLET
2018-03-16 23:42 ` kbuild test robot
2018-03-17 1:39 ` kbuild test robot
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=89a63178-a08a-5023-a045-018b4d7b11bc@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@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
all inboxes | Powered by JetHome®