[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<DU0PR04MB9417D5D76707C413ABC0BAC0881F2@DU0PR04MB9417.eurprd04.prod.outlook.com>
Date: Fri, 3 May 2024 23:11:40 +0000
From: Peng Fan <peng.fan@....com>
To: Linus Walleij <linus.walleij@...aro.org>, "Peng Fan (OSS)"
<peng.fan@....nxp.com>
CC: Thierry Reding <thierry.reding@...il.com>, Jonathan Hunter
<jonathanh@...dia.com>, Dvorkin Dmitry <dvorkin@...bo.com>, Wells Lu
<wellslutw@...il.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre
Torgue <alexandre.torgue@...s.st.com>, Emil Renner Berthing
<kernel@...il.dk>, Jianlong Huang <jianlong.huang@...rfivetech.com>, Hal Feng
<hal.feng@...rfivetech.com>, Orson Zhai <orsonzhai@...il.com>, Baolin Wang
<baolin.wang@...ux.alibaba.com>, Chunyan Zhang <zhang.lyra@...il.com>, Viresh
Kumar <vireshk@...nel.org>, Shiraz Hashim <shiraz.linux.kernel@...il.com>,
"soc@...nel.org" <soc@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>, Alim Akhtar
<alim.akhtar@...sung.com>, Geert Uytterhoeven <geert+renesas@...der.be>,
Patrice Chotard <patrice.chotard@...s.st.com>, Heiko Stuebner
<heiko@...ech.de>, Damien Le Moal <dlemoal@...nel.org>, Ludovic Desroches
<ludovic.desroches@...rochip.com>, Nicolas Ferre
<nicolas.ferre@...rochip.com>, Alexandre Belloni
<alexandre.belloni@...tlin.com>, Claudiu Beznea <claudiu.beznea@...on.dev>,
Aisheng Dong <aisheng.dong@....com>, Fabio Estevam <festevam@...il.com>,
Shawn Guo <shawnguo@...nel.org>, Jacky Bai <ping.bai@....com>, Pengutronix
Kernel Team <kernel@...gutronix.de>, Chester Lin <chester62515@...il.com>,
Matthias Brugger <mbrugger@...e.com>, "Ghennadi Procopciuc (OSS)"
<ghennadi.procopciuc@....nxp.com>, Sean Wang <sean.wang@...nel.org>, Matthias
Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>, Sascha Hauer
<s.hauer@...gutronix.de>, Andrew Jeffery <andrew@...econstruct.com.au>, Joel
Stanley <joel@....id.au>, Dan Carpenter <dan.carpenter@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-stm32@...md-mailman.stormreply.com"
<linux-stm32@...md-mailman.stormreply.com>,
"linux-samsung-soc@...r.kernel.org" <linux-samsung-soc@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
"linux-rockchip@...ts.infradead.org" <linux-rockchip@...ts.infradead.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>, "linux-aspeed@...ts.ozlabs.org"
<linux-aspeed@...ts.ozlabs.org>, "openbmc@...ts.ozlabs.org"
<openbmc@...ts.ozlabs.org>
Subject: RE: [PATCH 00/21] pinctrl: Use scope based of_node_put() cleanups
Hi Linus,
> Subject: Re: [PATCH 00/21] pinctrl: Use scope based of_node_put() cleanups
>
> Hi Peng,
>
> thanks for doing this! I am very much in favor of using scoped management
> of resources where it makes it easier to do the right thing.
>
> I agree with Krzysztof's comment that we should avoid scoping in cases where
> there is a clear path grab/use/release so the code is easy to read already as it
> is. Let's drop those.
Yeah, will drop them in v2.
>
> I saw there was some patch that was even a fix, perhaps I should pick that
> one separately for fixes, but probably it is non-urgent.
Not urgent, I will add fix tag in v2.
Thanks,
Peng.
>
> I suppose we will just apply v2 after people had some time to look at it!
>
> Yours,
> Linus Walleij
Powered by blists - more mailing lists