linux-kernel - Re: [PATCH] regulator: core: fix the broken behavior of regulator_dev

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: <172607190695.111510.14458343975352541206.b4-ty@kernel.org>
Date: Wed, 11 Sep 2024 17:25:06 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, wenst@...omium.org, Wei Fang <wei.fang@....com>
Cc: aisheng.dong@....com, linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH] regulator: core: fix the broken behavior of
 regulator_dev_lookup()

On Wed, 11 Sep 2024 20:03:38 +0800, Wei Fang wrote:
> The behavior of regulator_dev_lookup() for non-DT way has been broken
> since the commit b8c325545714 ("regulator: Move OF-specific regulator
> lookup code to of_regulator.c").
> 
> Before the commit, of_get_regulator() was used to get the regulator,
> which returns NULL if the regulator is not found. So the regulator
> will be looked up through regulator_lookup_by_name() if no matching
> regulator is found in regulator_map_list.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: fix the broken behavior of regulator_dev_lookup()
      commit: a1d12410d9b1ecff87d39f80b0d1cec895012ffa

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