[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166749194409.389017.2951606632954136901.b4-ty@kernel.org>
Date: Thu, 03 Nov 2022 16:12:24 +0000
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh+dt@...nel.org>,
Zev Weiss <zev@...ilderbeest.net>, devicetree@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: Mike Rapoport <rppt@...nel.org>,
Patrick Rudolph <patrick.rudolph@...ements.com>,
Laxman Dewangan <ldewangan@...dia.com>,
linux-kernel@...r.kernel.org, openbmc@...ts.ozlabs.org,
Naresh Solanki <naresh.solanki@...ements.com>
Subject: Re: [PATCH v2 0/3] regulator: Add DT support for regulator-output connectors
On Mon, 31 Oct 2022 16:37:01 -0700, Zev Weiss wrote:
> This is v2 of my recent series adding support for userspace-controlled
> regulator-supplied power outputs [2]. This is an important feature
> for some kinds of BMC (baseboard management controller) systems where
> the BMC provides an operator with manual control of a set of DC power
> outputs.
>
> As in a broadly similar patchset that was recently almost merged [0],
> this takes the approach of providing support by extending the existing
> userspace-consumer regulator driver. A couple questions about the
> userspace-consumer driver came up along the way, however.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/3] regulator: devres: Add devm_regulator_bulk_get_exclusive()
commit: fd1845069711cdf1b1aaaa0f22311b7736396331
[2/3] dt-bindings: regulator: Add regulator-output binding
commit: 14b8ad4c2580231fc45c2313ef822a15bb12f63f
[3/3] regulator: userspace-consumer: Handle regulator-output DT nodes
commit: 5c51d4afcf3fd36159713556402e16cfab794ae9
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists