linux-kernel - Re: [PATCH v7 0/2] Add Richtek RTQ2208 SubPMIC 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: <169143879211.313569.6869257260821190569.b4-ty@kernel.org>
Date:   Mon, 07 Aug 2023 21:06:32 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
        Alina Yu <alina_yu@...htek.com>
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v7 0/2] Add Richtek RTQ2208 SubPMIC support

On Mon, 07 Aug 2023 14:28:05 +0800, Alina Yu wrote:
> This patch series adds support for RTQ2208 SubPMIC regulators.
> The RTQ2208 is a multi-phase, programmable power management IC that
> integrate with dual multi-configurable, synchronous buck converters
> and two ldos. The bucks features wide output voltage range from 0.4V to 2.05V
> and the capability to configure the corresponding power stages.
> 
> Thank you,
> Alina yu
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC
      commit: 4b591ed6971191134e331f02300b4ec4dee188ea
[2/2] regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver
      commit: 85a11f55621a0c18b22b43ab4219450ac1d19386

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