linux-kernel - Re: (subset) [PATCH 0/2] arm64: dts: qcom: clean up 'regulator-allowed-modes' indentation

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <166861089087.540847.301727183033006932.b4-ty@kernel.org>
Date:   Wed, 16 Nov 2022 15:01:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Bjorn Andersson <andersson@...nel.org>,
        Johan Hovold <johan+linaro@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Douglas Anderson <dianders@...omium.org>,
        devicetree@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
        linux-arm-msm@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Parikshit Pareek <quic_ppareek@...cinc.com>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Andy Gross <agross@...nel.org>
Subject: Re: (subset) [PATCH 0/2] arm64: dts: qcom: clean up 'regulator-allowed-modes' indentation

On Wed, 16 Nov 2022 11:20:52 +0100, Johan Hovold wrote:
> When reviewing a new devicetree for sa8540p-ride I noticed that the
> indentation for the 'regulator-allowed-modes' properties was off and
> realised that this had been copied from the recent patches adding the
> missing modes properties.
> 
> Let's clean up the binding example and current devicetree sources to
> avoid this pattern being reproduced further.
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/2] regulator: dt-bindings: qcom,rpmh: clean up example indentation
      commit: b8dfb3bed5524589052dafa0e4d6c4e25ae11544

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