linux-kernel - Re: (subset) [PATCH v2 0/4] Add Richtek RT5120 PMIC support

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <165599062767.127406.12571486984170083213.b4-ty@kernel.org>
Date:   Thu, 23 Jun 2022 14:23:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        dmitry.torokhov@...il.com, u0084500@...il.com, lee.jones@...aro.org
Cc:     linux-input@...r.kernel.org, cy_huang@...htek.com,
        linux-kernel@...r.kernel.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/4] Add Richtek RT5120 PMIC support

On Wed, 22 Jun 2022 18:01:40 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> This patch series is to add Richtek RT5120 PMIC support.
> In RT5120, it integrates four channels of buck converter, one channel of LDO,
> and one external enable channel to control the external power source.
> 
> Since v2:
> - Add 'unevaluatedProperties: false' for regulator buck1~4/ldo/exten.
> - Fix indention and remove status for powerkey.
> - Refine powerkey description for more HW details.
> - For the regulator property parsing, use of_property_read_u32 instead.
> - Not to overwrite regulator constraint.
> - Refine regulator desc coding.
> 
> [...]

Applied to

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

Thanks!

[3/4] regulator: rt5120: Add PMIC regulator support
      commit: c0216c0e68f736d20ac02bbaaaf4a216c10e53af

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