From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
linux-renesas-soc@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
kernel@pengutronix.de
Subject: [PATCH 0/8] regulator: Convert to platform remove callback returning void
Date: Tue, 5 Dec 2023 13:26:15 +0100 [thread overview]
Message-ID: <cover.1701778038.git.u.kleine-koenig@pengutronix.de> (raw)
Hello,
this series converts all drivers below drivers/regulator to struct
platform_driver::remove_new(). See commit 5c5a7680e67b ("platform:
Provide a remove callback that returns no value") for an extended
explanation and the eventual goal.
All conversations are trivial, because all .remove() callbacks returned
zero unconditionally.
There are no interdependencies between these patches, so they could be
picked up individually. However I'd expect them to go in all together
via Mark's regulator tree.
Best regards
Uwe
Uwe Kleine-König (8):
regulator: arizona-ldo1: Convert to platform remove callback returning
void
regulator: bd9571mwv: Convert to platform remove callback returning
void
regulator: db8500-prcmu: Convert to platform remove callback returning
void
regulator: stm32-vrefbuf: Convert to platform remove callback
returning void
regulator: uniphier: Convert to platform remove callback returning
void
regulator: userspace-consumer: Convert to platform remove callback
returning void
regulator: virtual: Convert to platform remove callback returning void
regulator: wm8350: Convert to platform remove callback returning void
drivers/regulator/arizona-ldo1.c | 8 +++-----
drivers/regulator/bd9571mwv-regulator.c | 5 ++---
drivers/regulator/db8500-prcmu.c | 6 ++----
drivers/regulator/stm32-vrefbuf.c | 6 ++----
drivers/regulator/uniphier-regulator.c | 6 ++----
drivers/regulator/userspace-consumer.c | 6 ++----
drivers/regulator/virtual.c | 6 ++----
drivers/regulator/wm8350-regulator.c | 6 ++----
8 files changed, 17 insertions(+), 32 deletions(-)
base-commit: 0f5f12ac05f36f117e793656c3f560625e927f1b
--
2.42.0
next reply other threads:[~2023-12-05 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 12:26 Uwe Kleine-König [this message]
2023-12-05 12:26 ` [PATCH 1/8] regulator: arizona-ldo1: " Uwe Kleine-König
2023-12-05 13:06 ` Charles Keepax
2023-12-05 12:26 ` [PATCH 2/8] regulator: bd9571mwv: " Uwe Kleine-König
2023-12-05 14:16 ` Geert Uytterhoeven
2023-12-05 12:26 ` [PATCH 3/8] regulator: db8500-prcmu: " Uwe Kleine-König
2023-12-05 12:26 ` [PATCH 4/8] regulator: stm32-vrefbuf: " Uwe Kleine-König
2023-12-05 12:26 ` [PATCH 5/8] regulator: uniphier: " Uwe Kleine-König
2023-12-05 12:26 ` [PATCH 6/8] regulator: userspace-consumer: " Uwe Kleine-König
2023-12-05 12:26 ` [PATCH 7/8] regulator: virtual: " Uwe Kleine-König
2023-12-05 12:26 ` [PATCH 8/8] regulator: wm8350: " Uwe Kleine-König
2023-12-05 13:06 ` Charles Keepax
2023-12-12 15:46 ` [PATCH 0/8] regulator: " Mark Brown
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=cover.1701778038.git.u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=patches@opensource.cirrus.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
all inboxes | Powered by JetHome®