linux-kernel - Re: [PATCH 0/2] Address some issues at hi6421v600 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] [day] [month] [year] [list]

Message-Id: <162730228789.6183.11432905675628892383.b4-ty@kernel.org>
Date:   Mon, 26 Jul 2021 17:08:31 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        linuxarm@...wei.com, mauro.chehab@...wei.com
Subject: Re: [PATCH 0/2] Address some issues at hi6421v600 regulator driver

On Sat, 24 Jul 2021 12:22:40 +0200, Mauro Carvalho Chehab wrote:
> Patch 1 on this series address a review made by Rob Herring for the dt-bindings.
> It basically use "ldo" instead of "LDO", in order to match the patch I wrote to
> dt-bindings:
> 	https://lore.kernel.org/lkml/b7a775808d9c3a87fbe1c5a6dd71f8f18be7e649.1627116034.git.mchehab+huawei@kernel.org/T/#u
> 
> Patch 2 is just a cleanup patch, changing the namespace for the voltage
> range arrays. IMO, the new names fit better than the previous ones.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: hi6421v600: use lowercase for ldo
      commit: ccb2a74eec211c368ddbe3eaec4a20292e431095
[2/2] regulator: hi6421v600: rename voltage range arrays
      commit: 5e36129f2b4e9629513670fc1df97545ab4bd5a1

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