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: Mon, 22 Aug 2022 13:17:01 -0500 From: Rob Herring <robh@...nel.org> To: Horatiu Vultur <horatiu.vultur@...rochip.com> Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, srinivas.kandagatla@...aro.org, krzysztof.kozlowski+dt@...aro.org Subject: Re: [PATCH 1/2] dt-bindings: lan966x-otpc: document Lan966X OTPC On Mon, Aug 22, 2022 at 08:04:56AM +0200, Horatiu Vultur wrote: > The 08/19/2022 09:52, Krzysztof Kozlowski wrote: > > Hi Krzysztof, > > > > > On 18/08/2022 19:44, Horatiu Vultur wrote: > > > Document Lan966x OTP controller. > > > > > > + > > > +properties: > > > + compatible: > > > + items: > > > + - const: microchip,lan966x-otpc > > > > No wildcards in compatible (which will also affect the file name as it > > should match the compatible). > > Ok, I will replace lan966x with lan966 as the SoC is defined (SOC_LAN966) Pretty sure that's still a wildcard for the SoC family. 9668 or 9662 are the ones we already have. Yes, there's already a bunch of 966x compatibles, but that's not a pattern that should continue. Rob
Powered by blists - more mailing lists