linux-kernel - Re: [PATCH v2 1/2] regulator: dt-bindings: Add Richtek RT4803

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]

Date:   Wed, 29 Mar 2023 17:50:51 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        cy_huang@...htek.com
Cc:     lgirdwood@...il.com, jeff_chang@...htek.com,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 1/2] regulator: dt-bindings: Add Richtek RT4803

On Wed, 29 Mar 2023 08:43:25 +0800, cy_huang@...htek.com wrote:
> Add the binding document for Richtek RT4803.
> 
> 

Applied to

   broonie/regulator.git for-6.4

Thanks!

[1/2] regulator: dt-bindings: Add Richtek RT4803
      commit: e126cdaad15c4206f27b450e5d87391d5066615c
[2/2] regulator: Add Richtek RT4803 boost regulator
      commit: 6928a3c082f19404bd41bf33beeae112915dc666

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