linux-kernel - Re: [PATCH v2] regulator: Don't error out fixed regulator in regulator_sync

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: <163501903135.919198.6701017250560518879.b4-ty@kernel.org>
Date:   Sat, 23 Oct 2021 20:58:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dmitry Osipenko <digetx@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Thierry Reding <treding@...dia.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-tegra@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] regulator: Don't error out fixed regulator in regulator_sync_voltage()

On Thu, 21 Oct 2021 21:33:08 +0300, Dmitry Osipenko wrote:
> Fixed regulator can't change voltage and regulator_sync_voltage()
> returns -EINVAL in this case. Make regulator_sync_voltage() to succeed
> for regulators that are incapable to change voltage.
> 
> On NVIDIA Tegra power management driver needs to sync voltage and we have
> one device (Trimslice) that uses fixed regulator which is getting synced.
> The syncing error isn't treated as fatal, but produces a noisy error
> message. This patch silences that error.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: Don't error out fixed regulator in regulator_sync_voltage()
      commit: 400d5a5da43c0e84e5aa75151082ea91f0fae3c9

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