From: Romain Gantois <romain.gantois@bootlin.com>
To: Felix Gu <gu_0233@qq.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, Felix Gu <gu_0233@qq.com>
Subject: Re: [PATCH] misc:ti_fpc202:fix a potential memory leak in probe function
Date: Fri, 26 Dec 2025 10:01:39 +0100 [thread overview]
Message-ID: <5036254.GXAFRqVoOG@fw-rgant> (raw)
In-Reply-To: <tencent_1EF3D5211C623411353E636680860BDCD106@qq.com>
[-- Attachment #1.1: Type: text/plain, Size: 1386 bytes --]
Hello Felix,
On Thursday, 25 December 2025 16:02:56 CET Felix Gu wrote:
> Use for_each_child_of_node_scoped() to simplify the code and ensure the
> device node reference is automatically released when the loop scope
> ends.
>
Nit: please put spaces between the tags in the commit log title, like so:
"misc: ti_fpc202: fix a potential memory leak ..."
> Signed-off-by: Felix Gu <gu_0233@qq.com>
> ---
> drivers/misc/ti_fpc202.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/misc/ti_fpc202.c b/drivers/misc/ti_fpc202.c
> index 7964e46c7448..8eb2b5ac9850 100644
> --- a/drivers/misc/ti_fpc202.c
> +++ b/drivers/misc/ti_fpc202.c
> @@ -309,7 +309,6 @@ static void fpc202_remove_port(struct fpc202_priv *priv,
> int port_id) static int fpc202_probe(struct i2c_client *client)
> {
> struct device *dev = &client->dev;
> - struct device_node *i2c_handle;
> struct fpc202_priv *priv;
> int ret, port_id;
>
> @@ -357,7 +356,7 @@ static int fpc202_probe(struct i2c_client *client)
>
> bitmap_zero(priv->probed_ports, FPC202_NUM_PORTS);
>
> - for_each_child_of_node(dev->of_node, i2c_handle) {
> + for_each_child_of_node_scoped(dev->of_node, i2c_handle) {
> ret = of_property_read_u32(i2c_handle, "reg", &port_id);
> if (ret) {
> if (ret == -EINVAL)
With the above fixed:
Reviewed-by: Romain Gantois <romain.gantois@bootlin.com>
[-- Attachment #1.2: Type: text/html, Size: 4646 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-26 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 15:02 Felix Gu
2025-12-26 9:01 ` Romain Gantois [this message]
2025-12-26 10:22 ` [PATCH v2] misc: ti_fpc202: fix " Felix Gu
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=5036254.GXAFRqVoOG@fw-rgant \
--to=romain.gantois@bootlin.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=gu_0233@qq.com \
--cc=linux-kernel@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®