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: Tue, 16 Aug 2022 19:40:25 +0100 From: "Lad, Prabhakar" <prabhakar.csengg@...il.com> To: Rob Herring <robh@...nel.org> Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>, Geert Uytterhoeven <geert+renesas@...der.be>, Magnus Damm <magnus.damm@...il.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Linux-Renesas <linux-renesas-soc@...r.kernel.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Biju Das <biju.das.jz@...renesas.com> Subject: Re: [PATCH] dt-bindings: soc: renesas: Move renesas.yaml from arm to soc Hi Rob, On Tue, Aug 16, 2022 at 6:41 PM Rob Herring <robh@...nel.org> wrote: > > On Mon, Aug 15, 2022 at 12:17:08PM +0100, Lad Prabhakar wrote: > > renesas.yaml lists out all the Renesas SoC's and the platforms/EVK's which > > is either ARM32/ARM64. It would rather make sense if we move renesas.yaml > > to the soc/renesas folder instead. This is in preparation for adding a new > > SoC (RZ/Five) from Renesas which is based on RISC-V. > > Please post this as part of the above. > Sure, I just wanted to get some feedback on this so had it posted separately. > bindings/soc/ is just a dumping ground for stuff that doesn't fit > anywhere. We've mostly cleaned bindings/arm/ of that, so I don't really > want to start that again. I would propose bindings/board/ instead if we > move in this direction. > OK. So to clarify, how do we separate it further bindings/board/<based on SoC vendor> or bindings/board/<board manufacturer>? Cheers, Prabhakar
Powered by blists - more mailing lists