[PATCH 0/2] regulator: Couple of fixes for of_regulator_bulk_get_all() API

Manivannan Sadhasivam posted 2 patches 1 year, 1 month ago
include/linux/regulator/consumer.h | 77 +++++++++++++-----------------
1 file changed, 32 insertions(+), 45 deletions(-)
[PATCH 0/2] regulator: Couple of fixes for of_regulator_bulk_get_all() API
Posted by Manivannan Sadhasivam 1 year, 1 month ago
Hi,

This series fixes a couple of issues in the consumer header file identified
while using the of_regulator_bulk_get_all() API in the PCI pwrctrl driver [1].
I'm sending the fixes separately since these are independent from that series.

- Mani

[1] https://lore.kernel.org/linux-pci/20241231-pci-pwrctrl-slot-v2-0-6a15088ba541@linaro.org/

Manivannan Sadhasivam (2):
  regulator: Guard of_regulator_bulk_get_all() with CONFIG_OF
  regulator: Move OF_ API declarations/definitions outside
    CONFIG_REGULATOR

 include/linux/regulator/consumer.h | 77 +++++++++++++-----------------
 1 file changed, 32 insertions(+), 45 deletions(-)

-- 
2.25.1
Re: [PATCH 0/2] regulator: Couple of fixes for of_regulator_bulk_get_all() API
Posted by Mark Brown 1 year, 1 month ago
On Sat, 04 Jan 2025 17:20:56 +0530, Manivannan Sadhasivam wrote:
> This series fixes a couple of issues in the consumer header file identified
> while using the of_regulator_bulk_get_all() API in the PCI pwrctrl driver [1].
> I'm sending the fixes separately since these are independent from that series.
> 
> - Mani
> 
> [1] https://lore.kernel.org/linux-pci/20241231-pci-pwrctrl-slot-v2-0-6a15088ba541@linaro.org/
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: Guard of_regulator_bulk_get_all() with CONFIG_OF
      commit: 1156b5e8be98c97087f8971609c852e418daf03b
[2/2] regulator: Move OF_ API declarations/definitions outside CONFIG_REGULATOR
      commit: 907af7d6e0c8cf4086b1bc5218281b2ca09f130b

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