All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: kernel@pengutronix.de, linux-imx@nxp.com,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kernel-janitors@vger.kernel.org,
	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: clk: imx: scu: Use common error handling code in __imx_clk_gpr_scu()
Date: Mon, 26 Feb 2024 11:08:44 +0200	[thread overview]
Message-ID: <ZdxVHLce6mk975Zp@linaro.org> (raw)
In-Reply-To: <1a3c05b8-45f8-4205-8cb5-3b8f2d791877@web.de>

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

WARNING: multiple messages have this Message-ID (diff)
From: Abel Vesa <abel.vesa@linaro.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: kernel@pengutronix.de, linux-imx@nxp.com,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kernel-janitors@vger.kernel.org,
	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: clk: imx: scu: Use common error handling code in __imx_clk_gpr_scu()
Date: Mon, 26 Feb 2024 11:08:44 +0200	[thread overview]
Message-ID: <ZdxVHLce6mk975Zp@linaro.org> (raw)
In-Reply-To: <1a3c05b8-45f8-4205-8cb5-3b8f2d791877@web.de>

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-26  9:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 17:19 [PATCH] clk: imx: scu: Fix memory leak in __imx_clk_gpr_scu() Kuan-Wei Chiu
2023-12-10 17:19 ` Kuan-Wei Chiu
2023-12-12  0:40 ` Peng Fan
2023-12-12  0:40   ` Peng Fan
2023-12-20  9:25 ` Abel Vesa
2023-12-20  9:25   ` Abel Vesa
2023-12-22  9:23 ` [cocci] [PATCH] clk: imx: scu: Use common error handling code " Markus Elfring
2023-12-22  9:23   ` Markus Elfring
2023-12-22  9:23   ` Markus Elfring
2024-02-02 18:45   ` Abel Vesa
2024-02-02 18:45     ` Abel Vesa
2024-02-02 20:21     ` [cocci] " Markus Elfring
2024-02-02 20:21       ` Markus Elfring
2024-02-02 20:21       ` Markus Elfring
2024-02-26  9:08       ` Abel Vesa [this message]
2024-02-26  9:08         ` Abel Vesa
2024-02-26 14:35         ` [cocci] " Markus Elfring
2024-02-26 14:35           ` Markus Elfring
2024-02-26 14:35           ` Markus Elfring

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=ZdxVHLce6mk975Zp@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=Markus.Elfring@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.