mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: "Jacopo Mondi" <jacopo+renesas@jmondi.org>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] media: i2c: max9286: Fix some redundant of_node_put() calls
Date: Mon, 28 Aug 2023 11:51:53 +0100	[thread overview]
Message-ID: <169321991310.137962.4278774029844229066@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <rveb47frebdzhpcxdt4jnyasiztrhfnee3pzgl5ndafh2jbrsf@za4o23cw3lch>

Quoting Jacopo Mondi (2023-08-28 08:34:40)
> Hi Christophe
> 
> On Sat, Aug 26, 2023 at 12:13:40AM +0200, Christophe JAILLET wrote:
> > This is odd to have a of_node_put() just after a for_each_child_of_node()
> > or a for_each_endpoint_of_node() loop. It should already be called
> > during the last iteration.
> 
> Let's unwrap the calls:
> 
> #define for_each_child_of_node(parent, child) \
>      for (child = of_get_next_child(parent, NULL); child != NULL; \
>           child = of_get_next_child(parent, child))
> 
> static struct device_node *__of_get_next_child(const struct device_node *node,
>                                                 struct device_node *prev)
> {
>         struct device_node *next;
> 
>         if (!node)
>                 return NULL;
> 
>         next = prev ? prev->sibling : node->child;
>         of_node_get(next);
>         of_node_put(prev);
>         return next;
> }
> 
> Let's express the C for loop semantic as a while to help following the
> code:
> 
>         child = of_get_next_child(parent, NULL);
>         while (child != NULL)
>                 child = of_get_next_child(parent, child);
> 
> I concur that the last loop iteration the call to
> __of_get_next_child() will expand to
> 
>         next = NULL;
>         of_node_get(NULL);
>         of_node_put(prev)
> 
> So it seems to me it is not necessary to put the node after
> for_each_child_of_node() ?
> 
> In facts none of the other usages of for_each_child_of_node() in the
> kernel (the ones i checked at least) have a put() after the loop.

I agree. As long as the loops don't use any break statement - there
shouldn't be any _put() after the completion of the loop.

That would make a good cocci script - make sure these iterators do not
use 'break' internally - as that would then conflict!


Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

> 
> >
> > Remove these calls.
> >
> > Fixes: 66d8c9d2422d ("media: i2c: Add MAX9286 driver")
> > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> 
> Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> 
> Thanks
>   j
> 
> > ---
> > /!\  This patch is speculative, review with case  /!\
> > ---
> >  drivers/media/i2c/max9286.c | 2 --
> >  1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/media/i2c/max9286.c b/drivers/media/i2c/max9286.c
> > index 20e7c7cf5eeb..f27a69b1b727 100644
> > --- a/drivers/media/i2c/max9286.c
> > +++ b/drivers/media/i2c/max9286.c
> > @@ -1450,7 +1450,6 @@ static int max9286_parse_dt(struct max9286_priv *priv)
> >
> >               i2c_mux_mask |= BIT(id);
> >       }
> > -     of_node_put(node);
> >       of_node_put(i2c_mux);
> >
> >       /* Parse the endpoints */
> > @@ -1514,7 +1513,6 @@ static int max9286_parse_dt(struct max9286_priv *priv)
> >               priv->source_mask |= BIT(ep.port);
> >               priv->nsources++;
> >       }
> > -     of_node_put(node);
> >
> >       of_property_read_u32(dev->of_node, "maxim,bus-width", &priv->bus_width);
> >       switch (priv->bus_width) {
> > --
> > 2.34.1
> >

  reply	other threads:[~2023-08-28 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 22:13 Christophe JAILLET
2023-08-28  7:34 ` Jacopo Mondi
2023-08-28 10:51   ` Kieran Bingham [this message]
2023-08-28 10:59 ` Laurent Pinchart

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=169321991310.137962.4278774029844229066@ping.linuxembedded.co.uk \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=sakari.ailus@linux.intel.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

all inboxes | Powered by JetHome®