linux-kernel - Re: [PATCH] regulator: pwm: Fix machine constraints application

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: <159907285997.18126.1455609056387315109.b4-ty@kernel.org>
Date:   Wed, 02 Sep 2020 19:54:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     linux-kernel@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH] regulator: pwm: Fix machine constraints application

On Wed, 2 Sep 2020 15:09:52 +0200, Vincent Whitchurch wrote:
> If the zero duty cycle doesn't correspond to any voltage in the voltage
> table, the PWM regulator returns an -EINVAL from get_voltage_sel() which
> results in the core erroring out with a "failed to get the current
> voltage" and ending up not applying the machine constraints.
> 
> Instead, return -ENOTRECOVERABLE which makes the core set the voltage
> since it's at an unknown value.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: pwm: Fix machine constraints application
      commit: 59ae97a7a9e1499c2070e29841d1c4be4ae2994a

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