public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 01/30] clk: mediatek: Make mtk_clk_simple_remove() return void
Date: Mon, 13 Mar 2023 09:54:07 +0100	[thread overview]
Message-ID: <d0a2eb84-4420-8b6c-bd97-e58aa47be289@collabora.com> (raw)
In-Reply-To: <20230312161512.2715500-2-u.kleine-koenig@pengutronix.de>

Il 12/03/23 17:14, Uwe Kleine-König ha scritto:
> mtk_clk_simple_remove() returned zero unconditionally. Make it return no
> value instead and convert the respective drivers to .remove_new.
> 
> This makes the semantics in the callers of mtk_clk_simple_remove() clearer
> and prepares for the quest to make platform driver's remove function return
> void.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Hello Uwe,

since there's a big cleanup series that is well reviewed and that is touching
practically all MediaTek clock drivers, can you please rebase this commit over
[1]?

Thanks,
Angelo

[1]: https://patchwork.kernel.org/project/linux-mediatek/list/?series=726914


  reply	other threads:[~2023-03-13  8:58 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 16:14 [PATCH 00/30] clk: Convert to platform remove callback returning void Uwe Kleine-König
2023-03-12 16:14 ` [PATCH 01/30] clk: mediatek: Make mtk_clk_simple_remove() return void Uwe Kleine-König
2023-03-13  8:54   ` AngeloGioacchino Del Regno [this message]
2023-03-13  9:45     ` Uwe Kleine-König
2023-03-12 16:14 ` [PATCH 02/30] clk: tegra: Don't warn three times about failure to unregister Uwe Kleine-König
2023-03-29  2:34   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 03/30] clk: xilinx: Drop if block with always false condition Uwe Kleine-König
2023-03-29  2:35   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 04/30] clk: axs10x: Convert to platform remove callback returning void Uwe Kleine-König
2023-03-29  2:35   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 05/30] clk: bcm: " Uwe Kleine-König
2023-03-14 21:28   ` Florian Fainelli
2023-03-29  2:35   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 06/30] clk: axi-clkgen: " Uwe Kleine-König
2023-03-29  2:36   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 07/30] clk: axm5516: " Uwe Kleine-König
2023-03-29  2:36   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 08/30] clk: fixed-factor: " Uwe Kleine-König
2023-03-29  2:36   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 09/30] clk: fixed-mmio: " Uwe Kleine-König
2023-03-29  2:36   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 10/30] clk: fixed-rate: " Uwe Kleine-König
2023-03-29  2:37   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 11/30] clk: hsdk-pll: " Uwe Kleine-König
2023-03-29  2:37   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 12/30] clk: palmas: " Uwe Kleine-König
2023-03-29  2:37   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 13/30] clk: pwm: " Uwe Kleine-König
2023-03-29  2:37   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 14/30] clk: s2mps11: " Uwe Kleine-König
2023-03-12 16:22   ` Krzysztof Kozlowski
2023-03-29  2:37   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 15/30] clk: scpi: " Uwe Kleine-König
2023-03-16 15:01   ` Sudeep Holla
2023-03-16 15:48     ` Uwe Kleine-König
2023-03-17  0:31       ` Stephen Boyd
2023-03-29  2:38   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 16/30] clk: stm32mp1: " Uwe Kleine-König
2023-03-29  2:38   ` Stephen Boyd
2023-03-12 16:14 ` [PATCH 17/30] clk: hisilicon: " Uwe Kleine-König
2023-03-29  2:38   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 18/30] clk: keystone: " Uwe Kleine-König
2023-03-29  2:39   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 19/30] clk: mediatek: " Uwe Kleine-König
2023-03-29  2:39   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 20/30] clk: mmp: " Uwe Kleine-König
2023-03-29  2:39   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 21/30] clk: mvebu: " Uwe Kleine-König
2023-03-29  2:39   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 22/30] clk: qcom: " Uwe Kleine-König
2023-03-12 16:15 ` [PATCH 23/30] clk: renesas: " Uwe Kleine-König
2023-03-13  9:05   ` Geert Uytterhoeven
2023-03-12 16:15 ` [PATCH 24/30] clk: samsung: " Uwe Kleine-König
2023-03-12 16:33   ` (subset) " Krzysztof Kozlowski
2023-03-12 16:15 ` [PATCH 25/30] clk: stm32: " Uwe Kleine-König
2023-03-29  2:40   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 26/30] clk: tegra: " Uwe Kleine-König
2023-03-29  2:40   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 27/30] clk: ti: " Uwe Kleine-König
2023-03-29  2:40   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 28/30] clk: uniphier: " Uwe Kleine-König
2023-03-29  2:40   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 29/30] clk: x86: " Uwe Kleine-König
2023-03-29  2:40   ` Stephen Boyd
2023-03-12 16:15 ` [PATCH 30/30] clk: xilinx: " Uwe Kleine-König
2023-03-29  2:41   ` Stephen Boyd
2023-03-15 23:35 ` (subset) [PATCH 00/30] clk: " Bjorn Andersson

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=d0a2eb84-4420-8b6c-bd97-e58aa47be289@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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