linux-aspeed.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 08/21] pinctrl: samsung: Use scope based of_node_put() cleanups
Date: Wed, 01 May 2024 16:35:11 -0000	[thread overview]
Message-ID: <34193501-5b7b-4ffd-8549-a04c6930d02d@kernel.org> (raw)
In-Reply-To: <20240501-pinctrl-cleanup-v1-8-797ceca46e5c@nxp.com>

On 01/05/2024 14:56, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Use scope based of_node_put() cleanup to simplify code.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  drivers/pinctrl/samsung/pinctrl-exynos-arm.c |  3 +--
>  drivers/pinctrl/samsung/pinctrl-exynos.c     | 16 ++++------------
>  drivers/pinctrl/samsung/pinctrl-s3c64xx.c    |  8 ++------
>  drivers/pinctrl/samsung/pinctrl-samsung.c    | 26 +++++++-------------------
>  4 files changed, 14 insertions(+), 39 deletions(-)
> 
> diff --git a/drivers/pinctrl/samsung/pinctrl-exynos-arm.c b/drivers/pinctrl/samsung/pinctrl-exynos-arm.c
> index 85ddf49a5188..9a57b3ceb536 100644
> --- a/drivers/pinctrl/samsung/pinctrl-exynos-arm.c
> +++ b/drivers/pinctrl/samsung/pinctrl-exynos-arm.c
> @@ -56,7 +56,7 @@ s5pv210_retention_init(struct samsung_pinctrl_drv_data *drvdata,
>  		       const struct samsung_retention_data *data)
>  {
>  	struct samsung_retention_ctrl *ctrl;
> -	struct device_node *np;
> +	struct device_node *np __free(device_node) = NULL;
>  	void __iomem *clk_base;
>  
>  	ctrl = devm_kzalloc(drvdata->dev, sizeof(*ctrl), GFP_KERNEL);
> @@ -71,7 +71,6 @@ s5pv210_retention_init(struct samsung_pinctrl_drv_data *drvdata,
>  	}
>  
>  	clk_base = of_iomap(np, 0);
> -	of_node_put(np);

I don't think the code as simpler. Previous was very easy to read,
obvious, no error paths.

To me any conversion of such of_node_get immediately followed by
of_node_put is unwelcomed. Easy code is being  converted to complicated one.


Best regards,
Krzysztof


  reply	other threads:[~2024-05-01 16:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 12:48 [PATCH 00/21] pinctrl: Use scope based of_node_put() cleanups Peng Fan
2024-05-01 12:48 ` [PATCH 01/21] pinctrl: ti: iodelay: " Peng Fan
2024-05-01 13:32   ` Dan Carpenter
2024-05-02  0:29     ` Peng Fan
2024-05-02  7:05       ` Dan Carpenter
2024-05-01 12:49 ` [PATCH 02/21] pinctrl: tegra: " Peng Fan
2024-05-01 12:49 ` [PATCH 03/21] pinctrl: sunplus: " Peng Fan
2024-05-01 12:49 ` [PATCH 04/21] pinctrl: stm32: " Peng Fan
2024-05-01 12:50 ` [PATCH 05/21] pinctrl: starfive: " Peng Fan
2024-05-01 13:31   ` Emil Renner Berthing
2024-05-01 12:50 ` [PATCH 06/21] pinctrl: sprd: " Peng Fan
2024-05-01 12:50 ` [PATCH 07/21] pinctrl: spear: " Peng Fan
2024-05-01 12:50 ` [PATCH 08/21] pinctrl: samsung: " Peng Fan
2024-05-01 16:35   ` Krzysztof Kozlowski [this message]
2024-05-01 23:25     ` Peng Fan
2024-05-01 12:51 ` [PATCH 09/21] pinctrl: renesas: " Peng Fan
2024-05-01 12:51 ` [PATCH 10/21] pinctrl: st: " Peng Fan
2024-05-01 17:17   ` Dan Carpenter
2024-05-01 12:51 ` [PATCH 11/21] pinctrl: rockchip: " Peng Fan
2024-05-01 12:51 ` [PATCH 12/21] pinctrl: k210: " Peng Fan
2024-05-02  9:45   ` Damien Le Moal
2024-05-01 12:52 ` [PATCH 13/21] pinctrl: equilibrium: " Peng Fan
2024-05-01 12:52 ` [PATCH 14/21] pinctrl: at91: " Peng Fan
2024-05-01 12:52 ` [PATCH 15/21] pinctrl: s32cc: " Peng Fan
2024-05-01 12:52 ` [PATCH 16/21] pinctrl: nomadik: " Peng Fan
2024-05-01 12:53 ` [PATCH 18/21] pinctrl: freescale: " Peng Fan
2024-05-01 12:53 ` [PATCH 17/21] pinctrl: mediatek: " Peng Fan
2024-05-01 12:53 ` [PATCH 20/21] pinctrl: aspeed: g5: " Peng Fan
2024-05-02  0:54   ` Andrew Jeffery
2024-05-02 11:53     ` Peng Fan
2024-05-01 12:53 ` [PATCH 19/21] pinctrl: bcm: bcm63xx: " Peng Fan
2024-05-01 12:54 ` [PATCH 21/21] pinctrl: pinconf-generic: " Peng Fan
2024-05-03  7:20 ` [PATCH 00/21] pinctrl: " Linus Walleij
2024-05-03 23:12   ` Peng Fan

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=34193501-5b7b-4ffd-8549-a04c6930d02d@kernel.org \
    --to=krzk@kernel.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).