linux-kernel - Re: [PATCH 1/3] regulator: rt4801: Add support for RT4801 Display Bias regulator driver

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]

Date:   Tue, 18 Aug 2020 17:56:08 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, robh+dt@...nel.org,
        cy_huang <u0084500@...il.com>
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        cy_huang@...htek.com, gene_chen@...htek.com
Subject: Re: [PATCH 1/3] regulator: rt4801: Add support for RT4801 Display Bias regulator driver

On Sat, 15 Aug 2020 11:14:20 +0800, cy_huang wrote:
> Adds support for the RT4801 DSV. It has two regulators (DSVP/DSVN) with
> an I2C interface. DSVP/DSVN can provide the display panel module for the
> positive/negative voltage range from (+/-)4V to (+/-)6V.

Applied to

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

Thanks!

[1/3] regulator: rt4801: Add support for RT4801 Display Bias regulator driver
      commit: 5bbbfc7f7f0a44b7a85ab3872dd2ccce7019f7b1
[2/3] regulator: rt4801: Add DT binding documentation
      commit: fd6b928db8a05fcd8629320c52eae214a8615aae
[3/3] regulator: rt4801: Fix the dt-binding document for dtc check.
      commit: 6f4ac2844b61d43c0c48b7c67a974d9f6e4ddd9c

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