linux-kernel - Re: [PATCH 0/3] Allow use of DVS GPIOs on the RK808 PMIC variant only

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172962272118.122698.2211173167773675100.b4-ty@kernel.org>
Date: Tue, 22 Oct 2024 19:45:21 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, Dragan Simic <dsimic@...jaro.org>
Cc: linux-rockchip@...ts.infradead.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Allow use of DVS GPIOs on the RK808 PMIC variant
 only

On Mon, 14 Oct 2024 12:43:38 +0200, Dragan Simic wrote:
> This is a small series that primarily makes the rk808-regulator driver
> more compliant to the DT bindings, by allowing use of DVS GPIOs on the
> RK808 variant only.  There's no point in allowing that on the other PMIC
> variants, because they don't support the DVS GPIOs, and it goes against
> the DT bindings to allow a possibly misplaced "dvs-gpios" property to
> actually be handled in the rk808-regulator driver.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: rk808: Perform trivial code cleanups
      commit: 1bc3f0e9868929211c6abeb7e79b566c27fe9bb4
[2/3] regulator: rk808: Use dev_err_probe() in the probe path
      commit: fde993ae0b6e5edab0563897e232b94d1d2165a4
[3/3] regulator: rk808: Restrict DVS GPIOs to the RK808 variant only
      commit: 33a846e88481cc4659c6d670759b6295903e43b9

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