linux-kernel - Re: [PATCH 0/4] regulator: devres: remove unused device-managed unregister APIs

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: <162608654077.4419.15973416226245111161.b4-ty@kernel.org>
Date:   Mon, 12 Jul 2021 11:45:45 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Alexandru Ardelean <aardelean@...iqon.com>,
        linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>, lgirdwood@...il.com
Subject: Re: [PATCH 0/4] regulator: devres: remove unused device-managed unregister APIs

On Fri, 25 Jun 2021 15:23:20 +0300, Alexandru Ardelean wrote:
> These APIs aren't used anywhere and most-likely exist because of the
> general principle of C APIs, where if an API function does an
> allocation/registration, it must also have an equivalent
> deallocation/deregistration counterpart.
> 
> For devm_ functions this isn't all that true (for all cases), as the idea
> of these function is to provide an auto-cleanup logic on drivers/system
> de-init.
> 
> [...]

Applied to

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

Thanks!

[1/4] regulator: devres: remove devm_regulator_unregister_notifier() function
      (no commit info)
[2/4] regulator: devres: remove devm_regulator_unregister() function
      commit: 4ff75a29976590bc7afe3ed75d547c1f2a924c75
[3/4] regulator: devres: remove devm_regulator_bulk_unregister_supply_alias()
      commit: eed43b96ede9c3f018ad24149de83f24b86ad729
[4/4] regulator: devres: unexport devm_regulator_unregister_supply_alias()
      commit: 4d9f4d1de3ceb84fa6ce68177a26b8fac6a71290

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