From: Pavel Machek <pavel@ucw.cz>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Jyri Sarha <jsarha@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
kbuild-all@01.org
Subject: Re: [PATCH] leds: tlc591xx: fix device_node_continue.cocci warnings (fwd)
Date: Thu, 6 Dec 2018 23:09:18 +0100 [thread overview]
Message-ID: <20181206220918.GA32650@amd> (raw)
In-Reply-To: <alpine.DEB.2.21.1812062126130.2464@hadrien>
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
On Thu 2018-12-06 21:28:16, Julia Lawall wrote:
> Hello,
>
> The code seems to be wrong in several ways. If the continue is wanted,
> the of_node_put is not needed; it will happen on the next iteration. If
> the continue is not wanted, the of_node_put is needed, and the continue
> should be dropped.
Yep, code is confusing. But the patch is bad, we don't want "continue; return;"
Hmm, continue seems more logical to me -- but I guess Jyri should
decde?
Pavel
> ---------- Forwarded message ----------
> Date: Thu, 6 Dec 2018 19:48:54 +0800
> From: kbuild test robot <lkp@intel.com>
> To: kbuild@01.org
> Cc: Julia Lawall <julia.lawall@lip6.fr>
> Subject: [PATCH] leds: tlc591xx: fix device_node_continue.cocci warnings
>
> CC: kbuild-all@01.org
> TO: Jyri Sarha <jsarha@ti.com>
> CC: Peter Ujfalusi <peter.ujfalusi@ti.com>
> CC: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> CC: Pavel Machek <pavel@ucw.cz>
> CC: linux-leds@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
>
> From: kbuild test robot <fengguang.wu@intel.com>
>
> drivers/leds/leds-tlc591xx.c:342:3-14: ERROR: probable double put.
>
> Device node iterators put the previous value of the index variable, so an
> explicit put causes a double put.
>
> Generated by: scripts/coccinelle/iterators/device_node_continue.cocci
>
> Fixes: 7b2d34aaede7 ("leds: tlc591xx: Add gpio output support")
> CC: Jyri Sarha <jsarha@ti.com>
> Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
> ---
>
> tree: https://github.com/omap-audio/linux-audio peter/ti-linux-4.19.y/wip
> head: 838f24e2deaf1229002bd6555eb7e889b09ac1f9
> commit: 7b2d34aaede727b4abfc78061bbd2202fcd92bc8 [62/67] leds: tlc591xx: Add gpio output support
> :::::: branch date: 26 hours ago
> :::::: commit date: 26 hours ago
>
> Please take the patch only if it's a positive warning. Thanks!
>
> leds-tlc591xx.c | 1 -
> 1 file changed, 1 deletion(-)
>
> --- a/drivers/leds/leds-tlc591xx.c
> +++ b/drivers/leds/leds-tlc591xx.c
> @@ -339,7 +339,6 @@ tlc591xx_probe(struct i2c_client *client
> for_each_child_of_node(np, child) {
> err = of_property_read_u32(child, "reg", ®);
> if (err) {
> - of_node_put(child);
> continue;
> return err;
> }
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-12-06 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 20:28 [PATCH] leds: tlc591xx: fix device_node_continue.cocci warnings (fwd) Julia Lawall
2018-12-06 22:09 ` Pavel Machek [this message]
2018-12-07 22:25 ` Jacek Anaszewski
2018-12-08 7:28 ` Julia Lawall
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=20181206220918.GA32650@amd \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=jsarha@ti.com \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.