linux-kernel - Re: [PATCH v2] dt-bindings: regulator: Fix qcom,spmi-regulator schema

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: <166195037974.99335.15195185114132333580.b4-ty@kernel.org>
Date:   Wed, 31 Aug 2022 13:52:59 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jean-Philippe Brucker <jean-philippe@...aro.org>,
        lgirdwood@...il.com
Cc:     devicetree@...r.kernel.org, Rob Herring <robh@...nel.org>,
        robh+dt@...nel.org, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org, agross@...nel.org,
        konrad.dybcio@...ainline.org, bjorn.andersson@...aro.org,
        robimarko@...il.com, krzysztof.kozlowski+dt@...aro.org
Subject: Re: [PATCH v2] dt-bindings: regulator: Fix qcom,spmi-regulator schema

On Wed, 31 Aug 2022 09:05:04 +0100, Jean-Philippe Brucker wrote:
> The DT validator reports an error in the schema:
> 
> Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.yaml: ignoring, error in schema: patternProperties: ^(5vs[1-2]|(l|s)[1-9][0-9]?|lvs[1-3])$: properties
> 
> Move the unevaluatedProperties statement out of the properties section
> to fix it.
> 
> [...]

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: Fix qcom,spmi-regulator schema
      commit: 475043fabe8c58fb18c32c7942d8754897bd11fa

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