linux-kernel - Re: (subset) [PATCH v5 1/6] mfd: rt4831: Adds support for Richtek RT4831 core

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:   Mon, 28 Dec 2020 16:13:46 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, jingoohan1@...il.com,
        cy_huang <u0084500@...il.com>, lee.jones@...aro.org,
        b.zolnierkie@...sung.com, daniel.thompson@...aro.org
Cc:     linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org,
        ChiYuan Huang <cy_huang@...htek.com>
Subject: Re: (subset) [PATCH v5 1/6] mfd: rt4831: Adds support for Richtek RT4831 core

On Thu, 17 Dec 2020 23:00:39 +0800, cy_huang wrote:
> This adds support Richtek RT4831 core. It includes four channel WLED driver
> and Display Bias Voltage outputs.

Applied to

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

Thanks!

[3/6] regulator: rt4831: Adds DT binding document for Richtek RT4831 DSV regulator
      commit: 934b05e818620e922151734b2d0e070e388e3c53
[6/6] regulator: rt4831: Adds support for Richtek RT4831 DSV regulator
      commit: 9351ab8b0cb61ffbef30343d28d1855e329c98fb

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