Messages in this thread | | | From | Mark Brown <> | Subject | Re: [PATCH] regulator: core: Make regulator_lock_two() logic easier to follow | Date | Tue, 18 Apr 2023 17:21:32 +0100 |
| |
On Thu, 13 Apr 2023 17:34:17 -0700, Douglas Anderson wrote: > The regulator_lock_two() function could be made clearer in the case of > lock contention by having a local variable for each of the held and > contended locks. Let's do that. At the same time, let's use the swap() > function instead of open coding it. > > This change is expected to be a no-op and simply improves code > clarity. > > [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: core: Make regulator_lock_two() logic easier to follow commit: 37473397b852f556d8b9428ccbfd51886037842d
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
| |