linux-kernel - Re: [PATCH v2 0/2] Add Richtek RT5190A 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] [day] [month] [year] [list]

Message-Id: <164691213322.14059.3681107079269316589.b4-ty@kernel.org>
Date:   Thu, 10 Mar 2022 11:35:33 +0000
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, cy_huang <u0084500@...il.com>
Cc:     cy_huang@...htek.com, linux-kernel@...r.kernel.org,
        lgirdwood@...il.com, krzysztof.kozlowski@...onical.com,
        devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Add Richtek RT5190A PMIC support

On Wed, 9 Mar 2022 16:01:41 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> This patch series add Richtek RT5190A PMIC support.
> 
> v2:
> 1. use standard bindings regulator-min/max-microvolt to replace
>    fixed-microvolt property
> 2. change dt-bindings sample node name from rt5190a@64 to pmic@64.
> 3. add dt-binding header to defin e the opmode mapping number.
> 4. refine 'richtek,mute-enable' description in dt-binding.
> 4. due to fixed-microvolt property removal, use of_regulator_match to get
>    the regulator init data.
> 5. fix checkpatch warning and error.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: Add bindings for Richtek RT5190A PMIC
      commit: b77e70f6b8f2cc62fba847f3008a430a09ef275d
[2/2] regulator: rt5190a: Add support for Richtek RT5190A PMIC
      commit: 760423dfad53877b468490758fe7ea968ded9402

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