public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>, Jyri Sarha <jsarha@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Pavel Machek <pavel@ucw.cz>,
	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: Fri, 7 Dec 2018 23:25:50 +0100	[thread overview]
Message-ID: <c29a8fb6-4de1-2bc3-720a-1484bb30d38e@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1812062126130.2464@hadrien>

Hi Julia,

Thank you for the patch, but it doesn't apply to LED tree.

The patch causing the problem is out-of-LED-tree.

Best regards,
Jacek Anaszewski

On 12/6/18 9:28 PM, 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.
> 
> julia
> 
> ---------- 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", &reg);
>   		if (err) {
> -			of_node_put(child);
>   			continue;
>   			return err;
>   		}
> 



  parent reply	other threads:[~2018-12-07 22:25 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
2018-12-07 22:25 ` Jacek Anaszewski [this message]
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=c29a8fb6-4de1-2bc3-720a-1484bb30d38e@gmail.com \
    --to=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=pavel@ucw.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox