linux-kernel - Re: [PATCH] regulator: userspace-consumer: quiet device deferral

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: <171931524836.64387.7654955890138539082.b4-ty@kernel.org>
Date: Tue, 25 Jun 2024 12:34:08 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, linux-kernel@...r.kernel.org, 
 Robert Marko <robimarko@...il.com>
Subject: Re: [PATCH] regulator: userspace-consumer: quiet device deferral

On Sun, 23 Jun 2024 16:09:35 +0200, Robert Marko wrote:
> Trying to use userspace-consumer when the required supplies have not yet
> been probed will throw an error message on deferral:
> reg-userspace-consumer output-led-power: Failed to get supplies: -517
> 
> So, lets simply use dev_err_probe() instead of dev_err() to not print
> errors in case when driver probe is being deferred.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: userspace-consumer: quiet device deferral
      commit: 61a98ffc2081ac1e9070150932d9eb91d3935cf8

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