From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Markus Elfring <Markus.Elfring@web.de>,
linuxppc-dev@lists.ozlabs.org,
Jani Nikula <jani.nikula@intel.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Naveen N Rao <naveen@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH] powermac: Call of_node_put(bk_node) only once in pmac_has_backlight_type()
Date: Wed, 2 Oct 2024 22:43:46 +0200 [thread overview]
Message-ID: <d9bdc1b6-ea7e-47aa-80aa-02ae649abf72@csgroup.eu> (raw)
In-Reply-To: <b7e69e04-e15c-41ec-b62b-37253debc654@web.de>
Le 02/10/2024 à 22:02, Markus Elfring a écrit :
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Wed, 2 Oct 2024 21:50:27 +0200
>
> An of_node_put(bk_node) call was immediately used after a pointer check
> for an of_get_property() call in this function implementation.
> Thus call such a function only once instead directly before the check.
It seems pointless to perform a put immediately after a get. Shouldn't
of_find_property() be used instead ? And then of_property_read_string()
would probably be better.
Maybe you can even use of_property_match_string().
>
> This issue was transformed by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> arch/powerpc/platforms/powermac/backlight.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/powerpc/platforms/powermac/backlight.c b/arch/powerpc/platforms/powermac/backlight.c
> index 12bc01353bd3..d3666595a62e 100644
> --- a/arch/powerpc/platforms/powermac/backlight.c
> +++ b/arch/powerpc/platforms/powermac/backlight.c
> @@ -61,11 +61,9 @@ int pmac_has_backlight_type(const char *type)
> if (bk_node) {
> const char *prop = of_get_property(bk_node,
> "backlight-control", NULL);
> - if (prop && strncmp(prop, type, strlen(type)) == 0) {
> - of_node_put(bk_node);
> - return 1;
> - }
> of_node_put(bk_node);
> + if (prop && strncmp(prop, type, strlen(type)) == 0)
> + return 1;
> }
>
> return 0;
> --
> 2.46.1
>
next prev parent reply other threads:[~2024-10-02 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 20:02 Markus Elfring
2024-10-02 20:43 ` Christophe Leroy [this message]
2024-10-03 5:56 ` Dan Carpenter
2024-10-03 6:53 ` Krzysztof Kozlowski
2024-10-07 7:15 ` Markus Elfring
2024-10-09 4:48 ` [PATCH] " Michael Ellerman
2024-10-11 16:18 ` [PATCH] powermac: Use of_property_match_string() " Markus Elfring
2024-10-11 16:25 ` Christophe Leroy
2024-10-13 13:41 ` Dan Carpenter
2024-11-17 12:09 ` Michael Ellerman
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=d9bdc1b6-ea7e-47aa-80aa-02ae649abf72@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Markus.Elfring@web.de \
--cc=jani.nikula@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tzimmermann@suse.de \
/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®