linux-kernel - Re: [PATCH] regulator: core.c: Replace references to non-existent function

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: <160978203769.14485.1414576589830773531.b4-ty@kernel.org>
Date:   Mon, 04 Jan 2021 17:40:37 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Daniel Scally <djrscally@...il.com>, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core.c: Replace references to non-existent function

On Sun, 3 Jan 2021 16:55:41 +0000, Daniel Scally wrote:
> The function regulator_set_device_supply() is referenced a few times in
> comments in regulator/core.c; however this function was removed a long
> time ago by commit a5766f11cfd3 ("regulator: core - Rework machine API to
> remove string based functions."). Update those references to point to
> set_consumer_device_supply(), which replaced the old function.

Applied to

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

Thanks!

[1/1] regulator: core.c: Replace references to non-existent function
      commit: 90cf443d841e41af7fceb26aed6553e43670fe42

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