linux-kernel - Re: [PATCH 0/3] regulator: bd9571mwv: Miscellaneous fixes and improvements

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: <161582739233.20279.12170851873434705801.b4-ty@kernel.org>
Date:   Mon, 15 Mar 2021 16:57:04 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Geert Uytterhoeven <geert+renesas@...der.be>,
        Marek Vasut <marek.vasut+renesas@...il.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-renesas-soc@...r.kernel.org,
        Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
        Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] regulator: bd9571mwv: Miscellaneous fixes and improvements

On Fri, 12 Mar 2021 14:02:39 +0100, Geert Uytterhoeven wrote:
> *** BLURB HERE ***
> 
> Geert Uytterhoeven (3):
>   regulator: bd9571mwv: Fix AVS and DVFS voltage range
>   regulator: bd9571mwv: Fix regulator name printed on registration
>     failure
>   regulator: bd9571mwv: Convert device attribute to sysfs_emit()
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: bd9571mwv: Fix AVS and DVFS voltage range
      commit: 3b6e7088afc919f5b52e4d2de8501ad34d35b09b
[2/3] regulator: bd9571mwv: Fix regulator name printed on registration failure
      commit: 9cbc23f7d51fb0b1363bdfdd0b770aa7b5982f2f
[3/3] regulator: bd9571mwv: Convert device attribute to sysfs_emit()
      commit: 1deceabbdc0dd3162def1e26acb2e57a93275909

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