linux-kernel - Re: [PATCH v1] regulator: consumer: Add missing stubs to regulator/consumer.h

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: <161125803281.35944.2080830659749037080.b4-ty@kernel.org>
Date:   Thu, 21 Jan 2021 19:40:32 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Dmitry Osipenko <digetx@...il.com>,
        Viresh Kumar <vireshk@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Stephen Boyd <sboyd@...nel.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] regulator: consumer: Add missing stubs to regulator/consumer.h

On Wed, 20 Jan 2021 23:58:44 +0300, Dmitry Osipenko wrote:
> Add missing stubs to regulator/consumer.h in order to fix COMPILE_TEST
> of the kernel. In particular this should fix compile-testing of OPP core
> because of a missing stub for regulator_sync_voltage().

Applied to

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

Thanks!

[1/1] regulator: consumer: Add missing stubs to regulator/consumer.h
      commit: 51dfb6ca3728bd0a0a3c23776a12d2a15a1d2457

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