linux-kernel - Re: [PATCH] regulator: scmi: Allow for zero voltage domains

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: <167478083297.1118403.15307034817786674476.b4-ty@kernel.org>
Date:   Fri, 27 Jan 2023 00:53:52 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Cristian Marussi <cristian.marussi@....com>
Cc:     sudeep.holla@....com, Jim Quinlan <james.quinlan@...adcom.com>,
        Florian Fainelli <florian.fainelli@...adcom.com>
Subject: Re: [PATCH] regulator: scmi: Allow for zero voltage domains

On Thu, 26 Jan 2023 18:05:11 +0000, Cristian Marussi wrote:
> SCMI Voltage protocol allows the platform to report no voltage domains
> on discovery, while warning the user about such an odd configuration.
> As a consequence this condition should not be treated as error by the SCMI
> regulator driver either.
> 
> Allow SCMI regulator driver to probe successfully even when no voltage
> domains are discovered.
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: scmi: Allow for zero voltage domains
      commit: 668f777d02f61faa834f1e24f3b99576dbe5ff6b

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