[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZdxVHLce6mk975Zp@linaro.org>
Date: Mon, 26 Feb 2024 11:08:44 +0200
From: Abel Vesa <abel.vesa@...aro.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: kernel@...gutronix.de, linux-imx@....com, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
kernel-janitors@...r.kernel.org,
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()
On 24-02-02 21:21:19, Markus Elfring wrote:
> >> 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. The b4 tool will pick up the old patch if
you do this.
> Regards,
> Markus
Powered by blists - more mailing lists