[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z0IuNZq3g_0q0TkU@surfacebook.localdomain>
Date: Sat, 23 Nov 2024 21:34:13 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Javier Carrasco <javier.carrasco.cruz@...il.com>
Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Gene Chen <gene_chen@...htek.com>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Bartosz Golaszewski <brgl@...ev.pl>, Chen-Yu Tsai <wens@...e.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Samuel Holland <samuel@...lland.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-sunxi@...ts.linux.dev
Subject: Re: [PATCH 06/18] leds: el15203000: switch to
device_for_each_child_node_scoped()
Fri, Sep 27, 2024 at 01:20:57AM +0200, Javier Carrasco kirjoitti:
> Switch to device_for_each_child_node_scoped() to simplify the code by
> removing the need for calls to fwnode_handle_put() in the error paths.
>
> This also prevents possible memory leaks if new error paths are added
> without the required call to fwnode_handle_put().
>
> After switching to the scoped variant, there is no longer need for a
> jump to 'err_child_out', as an immediate return is possible.
...
> if (ret) {
> dev_err(priv->dev, "LED without ID number");
> - goto err_child_out;
> + return ret;
Now
return dev_err_probe(...);
> }
>
> if (led->reg > U8_MAX) {
> dev_err(priv->dev, "LED value %d is invalid", led->reg);
> - ret = -EINVAL;
> - goto err_child_out;
> + return -EINVAL;
Ditto.
> }
> dev_err(priv->dev,
> "failed to register LED device %s, err %d",
> led->ldev.name, ret);
> - goto err_child_out;
> + return ret;
Ditto.
return dev_err_probe(priv->dev, ret, "failed to register LED device %s\n",
led->ldev.name);
...
Also notice missed '\n' at the end of the strings (and yes, I know
that it's not a problem for dev_*() macros, but still...).
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists