From: Mark Brown <email@example.com> To: Alexandru Ardelean <firstname.lastname@example.org>, email@example.com Cc: Mark Brown <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH 0/4] regulator: devres: remove unused device-managed unregister APIs Date: Mon, 12 Jul 2021 11:45:45 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> 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
prev parent reply other threads:[~2021-07-12 10:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-25 12:23 Alexandru Ardelean 2021-06-25 12:23 ` [PATCH 1/4] regulator: devres: remove devm_regulator_unregister_notifier() function Alexandru Ardelean 2021-06-25 12:23 ` [PATCH 2/4] regulator: devres: remove devm_regulator_unregister() function Alexandru Ardelean 2021-06-25 12:23 ` [PATCH 3/4] regulator: devres: remove devm_regulator_bulk_unregister_supply_alias() Alexandru Ardelean 2021-06-25 12:23 ` [PATCH 4/4] regulator: devres: unexport devm_regulator_unregister_supply_alias() Alexandru Ardelean 2021-07-12 10:45 ` Mark Brown [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/4] regulator: devres: remove unused device-managed unregister APIs' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).