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
| ||
|
Message-ID: <29d1f7a3-e141-270c-9e71-e052fd41dd48@linaro.org> Date: Tue, 5 Jul 2022 13:52:59 +0200 From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> To: Pavel Machek <pavel@....cz>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, linux-leds@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Cc: ChiaEn Wu <peterwu.pub@...il.com>, Sven Schwermer <sven.schwermer@...ruptive-technologies.com>, Rob Herring <robh+dt@...nel.org>, Bjorn Andersson <bjorn.andersson@...aro.org>, Dan Murphy <dmurphy@...com>, Marek BehĂșn <kabel@...nel.org> Subject: Re: [PATCH] dt-bindings: leds: class-multicolor: reference class directly in multi-led node On 24/06/2022 13:21, Krzysztof Kozlowski wrote: > The leds/common.yaml is referenced directly in each LED node, which > leads to people doing the same with leds/leds-class-multicolor.yaml. > This is not correct because leds-class-multicolor.yaml defined multi-led > property and its children. Some schemas implemented this incorrect. > > Rework this to match same behavior common.yaml, so expect the multi-led > node to reference the leds-class-multicolor.yaml. Fixing allows to add > unevaluatedProperties:false. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> > > --- > > This will conflict with any new users of leds-class-multicolor, e.g.: > https://lore.kernel.org/all/20220623115631.22209-4-peterwu.pub@gmail.com/ > > The new users should be updated to match the usage introduced here. Pavel, Any comments from your side? It's waiting for a bit and folks are sending more and more wrong multicolor bindings... Best regards, Krzysztof
Powered by blists - more mailing lists