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: <20210925145233.vczhgui6cchkih5m@oxidize> Date: Sat, 25 Sep 2021 09:52:33 -0500 From: Nishanth Menon <nm@...com> To: Suman Anna <s-anna@...com> CC: Sinthu Raja <sinthu.raja@...tralsolutions.com>, Rob Herring <robh+dt@...nel.org>, Mathieu Poirier <mathieu.poirier@...aro.org>, Bjorn Andersson <bjorn.andersson@...aro.org>, Ohad Ben-Cohen <ohad@...ery.com>, <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, <linux-remoteproc@...r.kernel.org>, Sinthu Raja <sinthu.raja@...com>, "Nagalla, Hari" <hnagalla@...com> Subject: Re: [PATCH V3 2/2] dt-bindings: remoteproc: k3-dsp: Remove board-specific compatible from DT example On 12:54-20210924, Suman Anna wrote: > Hi Sinthu, > > On 9/24/21 12:25 PM, Suman Anna wrote: > > On 9/24/21 11:29 AM, Nishanth Menon wrote: > >> On 11:10-20210924, Suman Anna wrote: > >>> Hi Sinthu, > >>> > >>> On 9/17/21 4:54 AM, Sinthu Raja wrote: > >>>> From: Sinthu Raja <sinthu.raja@...com> > >>>> > >>>> The example includes a board-specific compatible property, this is > >>>> wrong as the example should be board agnostic and gets in the way of > >>>> additions for newer platforms. Replace the same with a generic soc > >>>> node. > >>> > >>> What board specific property? This description looks wrong. > > Can you please repost dropping the Fixes line, and modifying the patch > description as follows: > > dt-bindings: remoteproc: k3-dsp: Cleanup SoC compatible from DT example > > The K3 DSP binding example used the root-node with a SoC compatible > property originally to address the dt_binding_check warnings resulting > from using a value of 2 for #address-cells and #size-cells as per most > common usage on K3 SoCs. Clean this up and replace it with a generic soc > node to keep it agnostic of the SoC or board compatibles that are outside > the scope of this binding. This looks good to me as well. Thanks. -- Regards, Nishanth Menon Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists