From: Markus Elfring <Markus.Elfring@web.de>
To: Abel Vesa <abel.vesa@linaro.org>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org
Cc: Kuan-Wei Chiu <visitorckw@gmail.com>,
Abel Vesa <abelvesa@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Peng Fan <peng.fan@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [cocci] clk: imx: scu: Use common error handling code in __imx_clk_gpr_scu()
Date: Mon, 26 Feb 2024 15:35:43 +0100 [thread overview]
Message-ID: <1edb972e-7285-47d1-8ee6-606146b2f9e3@web.de> (raw)
In-Reply-To: <ZdxVHLce6mk975Zp@linaro.org>
>>>> 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
prev parent reply other threads:[~2024-02-26 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231210171907.3410922-1-visitorckw@gmail.com>
2023-12-22 9:23 ` [cocci] [PATCH] clk: imx: scu: Use common error handling code in __imx_clk_gpr_scu() Markus Elfring
[not found] ` <Zb04UUeE/cU9HtKZ@linaro.org>
2024-02-02 20:21 ` [cocci] " Markus Elfring
[not found] ` <ZdxVHLce6mk975Zp@linaro.org>
2024-02-26 14:35 ` Markus Elfring [this message]
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=1edb972e-7285-47d1-8ee6-606146b2f9e3@web.de \
--to=markus.elfring@web.de \
--cc=abel.vesa@linaro.org \
--cc=abelvesa@kernel.org \
--cc=cocci@inria.fr \
--cc=festevam@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=visitorckw@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).