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
| ||
|
Date: Fri, 2 Sep 2022 13:51:45 -0500 From: Andrew Halaney <ahalaney@...hat.com> To: agross@...nel.org, andersson@...nel.org, konrad.dybcio@...ainline.org, lgirdwood@...il.com, broonie@...nel.org, robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, dianders@...omium.org, johan@...nel.org, Andrew Halaney <ahalaney@...hat.com> Subject: [PATCH 0/3] regulator: dt-bindings: qcom,rpmh: dt-binding fixups Hi, This is my poor attempt at getting devicetree validation into a better state for qcom,rpmh-regulator.yaml. This is a follow-up to Johan's request for this over here: https://lore.kernel.org/linux-arm-msm/Yw8EE%2FESDUnIRf8P@hovoldconsulting.com/ In particular, I'm not certain patch 1 is the correct way to handle things, and patch 2 makes validation too wide for the *-supply nodes. I'd love any feedback here as I'm really not experienced in any of the spaces (regulator, rpmh, or dt schema) so nit picking is welcomed. Thanks in advance, Andrew Andrew Halaney (3): regulator: dt-bindings: qcom,rpmh: Use additionalProperties regulator: dt-bindings: qcom,rpmh: Specify supply property regulator: dt-bindings: qcom,rpmh: Indicate regulator-allow-set-load dependencies .../bindings/regulator/qcom,rpmh-regulator.yaml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) -- 2.37.2
Powered by blists - more mailing lists