From: 和亮 <windhl@126.com>
To: "Guenter Roeck" <linux@roeck-us.net>
Cc: tharvey@gateworks.com, rjones@gateworks.com, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] drivers: hwmon: Add missing of_node_put() in gsc-hwmon.c
Date: Thu, 16 Jun 2022 10:37:41 +0800 (CST) [thread overview]
Message-ID: <2da49756.221e.1816a5fa3d3.Coremail.windhl@126.com> (raw)
In-Reply-To: <01243e3e-f4d2-c1ba-98f5-db7bc0c62adc@roeck-us.net>
At 2022-06-16 01:57:49, "Guenter Roeck" <linux@roeck-us.net> wrote:
>
>Please use proper subject lines. Here it should have been
>
>hwmon: (gsc-hwmon) Add missing of_node_put()
Thanks, I will change it in my new patch.
>>> drivers/hwmon/gsc-hwmon.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/hwmon/gsc-hwmon.c b/drivers/hwmon/gsc-hwmon.c
>> index 1fe37418ff46..34c20d13627a 100644
>> --- a/drivers/hwmon/gsc-hwmon.c
>> +++ b/drivers/hwmon/gsc-hwmon.c
>> @@ -268,10 +268,14 @@ gsc_hwmon_get_devtree_pdata(struct device *dev)
>>
>> /* fan controller base address */
>> fan = of_find_compatible_node(dev->parent->of_node, NULL, "gw,gsc-fan");
>
>A single of_node_put(fan) here would have been be sufficient.
I think of_node_put after should come after its usage, right?
>>> - if (fan && of_property_read_u32(fan, "reg", &pdata->fan_base)) {
>> + if (fan && of_property_read_u32(fan, "reg", &pdata->fan_base)) {
>> + of_node_put(fan);
>> dev_err(dev, "fan node without base\n");
>> return ERR_PTR(-EINVAL);
>> }
>> +
>> + /* if fan&&!of_property_read_u32 fail */
>
>This comment only adds confusion and does not add any value.
Sorry, I just want to say, if *fan* is not NULL, but of_property_read_u32() returns 0.
In that case, we still need a of_node_put() to release fan, right?
>
>Guenter
>
>> + of_node_put(fan);
>>
>> /* allocate structures for channels and count instances of each type */
>> device_for_each_child_node(dev, child) {
Hi, Guenter, I am preparing my new patch and I want to discuss your suggestions as above.
next prev parent reply other threads:[~2022-06-16 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 15:18 [PATCH] drivers: hwmon: Add missing of_node_put() in gsc-hwmon.c Liang He
2022-06-15 17:57 ` Guenter Roeck
2022-06-16 2:37 ` 和亮 [this message]
2022-06-16 3:05 ` Guenter Roeck
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=2da49756.221e.1816a5fa3d3.Coremail.windhl@126.com \
--to=windhl@126.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rjones@gateworks.com \
--cc=tharvey@gateworks.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