linux-kernel - Re: [PATCH] regulator: tps65219: Report regulator name if devm_regulator

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: <167214225991.87975.6915126748096471073.b4-ty@kernel.org>
Date:   Tue, 27 Dec 2022 11:57:39 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
        Wadim Egorov <w.egorov@...tec.de>
Cc:     linux-arm-kernel@...ts.infradead.org, j-neanne@...libre.com,
        lgirdwood@...il.com, tony@...mide.com, upstream@...tec.de
Subject: Re: [PATCH] regulator: tps65219: Report regulator name if
 devm_regulator_register fails

On Wed, 14 Dec 2022 16:34:09 +0100, Wadim Egorov wrote:
> Make the error message more useful by reporting the actual regulator
> name if devm_regulator_register() fails.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: tps65219: Report regulator name if devm_regulator_register fails
      commit: cfbe9dfd664c7717ef297e01b7eecccc2b5fde6f

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