linux-kernel - Re: [PATCH v7 0/3] Add support for SCMI-Regulator

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: <160616798790.26619.2814900248177756212.b4-ty@kernel.org>
Date:   Mon, 23 Nov 2020 21:46:27 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org,
        Cristian Marussi <cristian.marussi@....com>
Cc:     Jonathan.Cameron@...wei.com, souvik.chakravarty@....com,
        sudeep.holla@....com, lukasz.luba@....com,
        etienne.carriere@...aro.org, james.quinlan@...adcom.com,
        satyakim@....qualcomm.com, vincent.guittot@...aro.org,
        f.fainelli@...il.com, robh@...nel.org
Subject: Re: [PATCH v7 0/3] Add support for SCMI-Regulator

On Mon, 23 Nov 2020 20:23:33 +0000, Cristian Marussi wrote:
> this series introduces the support for a new generic SCMI Regulator driver
> developed on top of the recently introduced SCMI Voltage Domain Protocol
> support as specified in the upcoming SCMIv3.0 specification. [1]
> 
> The underlying SCMI VD Protocol support, which was originally part of this
> series, is now applied on for-next/scmi-voltage [2], and this series,
> reduced to its SCMI Regulator support and dt-bindings fixes is similarly
> based on top of [2]:
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: arm: remove optional properties for SCMI Regulators
      commit: e8056bf01080eeb13b0229f3fa4cb25a5a2de6a5
[2/2] regulator: add SCMI driver
      commit: 0fbeae70ee7ce98e18a47337cd1f205dd88589e9

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