From: Brian Masney <bmasney@redhat.com>
To: Mark Brown <broonie@kernel.org>, Peng Fan <peng.fan@nxp.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Support Opensource <support.opensource@diasemi.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-msm@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] regulator: convert to subsys_platform_driver()
Date: Mon, 9 Nov 2026 16:20:11 -0500 [thread overview]
Message-ID: <avI5C2UFcxKF_LoG@redhat.com> (raw)
In-Reply-To: <1b56983f-f88b-453e-bd8f-8189c3f79d1b@sirena.org.uk>
Hi Mark,
On Mon, Nov 09, 2026 at 07:14:12PM +0000, Mark Brown wrote:
> On Fri, Nov 06, 2026 at 07:28:46PM -0500, Brian Masney wrote:
> > Reduce boilerplate code in these drivers and convert them over to use
> > the macro subsys_platform_driver().
>
> This doesn't apply against current code, please check and resend.
I see that Peng already posted a conversion for regulator. Based on
what's in next-20261109, it looks like there's 4 more drivers that can
be converted based on what I have in my patch.
drivers/regulator/qcom_rpm-regulator.c
drivers/regulator/qcom_smd-regulator.c
drivers/regulator/twl-regulator.c
drivers/regulator/twl6030-regulator.c
I'll post a v2 with just these 4 drivers.
Brian
next prev parent reply other threads:[~2026-11-09 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 0:28 Brian Masney
2026-11-07 10:47 ` Krzysztof Kozlowski
2026-11-09 11:24 ` Charles Keepax
2026-11-09 19:14 ` Mark Brown
2026-11-09 21:20 ` Brian Masney [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-04 11:33 [PATCH] regulator: Convert " Peng Fan (OSS)
2026-11-04 11:49 ` Charles Keepax
2026-11-07 14:18 ` 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=avI5C2UFcxKF_LoG@redhat.com \
--to=bmasney@redhat.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peng.fan@nxp.com \
--cc=rogerq@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=tony@atomide.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®