[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1edb972e-7285-47d1-8ee6-606146b2f9e3@web.de>
Date: Mon, 26 Feb 2024 15:35:43 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Abel Vesa <abel.vesa@...aro.org>, kernel@...gutronix.de,
linux-imx@....com, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kernel-janitors@...r.kernel.org
Cc: Kuan-Wei Chiu <visitorckw@...il.com>, Abel Vesa <abelvesa@...nel.org>,
Fabio Estevam <festevam@...il.com>,
Michael Turquette <mturquette@...libre.com>, Peng Fan <peng.fan@....com>,
Sascha Hauer <s.hauer@...gutronix.de>, Shawn Guo <shawnguo@...nel.org>,
Stephen Boyd <sboyd@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
cocci@...ia.fr
Subject: Re: clk: imx: scu: Use common error handling code in
__imx_clk_gpr_scu()
>>>> Use another label so that a bit of exception handling can be better reused
>>>> at the end of this function.
>>>
>>> Please don't send patches as reply to other(s) patches.
>>
>> This is a general possibility to connect an information sources with
>> a corresponding change idea.
>> Will the acceptance grow for the presented source code transformation?
>>
>
> Nope, please don't do that.
Do you find the proposed source code transformation reasonable (in principle)?
> The b4 tool will pick up the old patch if you do this.
Are you looking for further improvements for this development tool?
Regards,
Markus
Powered by blists - more mailing lists