linux-kernel - Re: [PATCH] regulator: fixed: use dev_err

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: <162386032647.25898.14083468115761592388.b4-ty@kernel.org>
Date:   Wed, 16 Jun 2021 17:41:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rouven Czerwinski <r.czerwinski@...gutronix.de>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        kernel@...gutronix.de
Subject: Re: [PATCH] regulator: fixed: use dev_err_probe for gpio

On Wed, 16 Jun 2021 14:53:31 +0200, Rouven Czerwinski wrote:
> Instead of returning the the PTR_ERR directly, use dev_err_probe which
> will also correctly set the deferred probe reason in
> /sys/kernel/debug/deferred_devices, making it easier to debug missing
> devices on the system.

Applied to

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

Thanks!

[1/1] regulator: fixed: use dev_err_probe for gpio
      commit: 7740ab84c13e32002742106afd443a4ca7fe3918

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