linux-kernel - Re: [PATCH v2 1/2] dt-bindings: sram: Document reg-io-width property

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8879cc2a-ba01-4760-ad4a-a40e1d2da3c5@broadcom.com>
Date: Tue, 13 Aug 2024 13:08:52 -0700
From: Florian Fainelli <florian.fainelli@...adcom.com>
To: "Rob Herring (Arm)" <robh@...nel.org>
Cc: bcm-kernel-feedback-list@...adcom.com,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Cristian Marussi <cristian.marussi@....com>, linux-kernel@...r.kernel.org,
 Conor Dooley <conor+dt@...nel.org>, arm-scmi@...r.kernel.org,
 Sudeep Holla <sudeep.holla@....com>, linux-arm-kernel@...ts.infradead.org,
 justin.chen@...adcom.com, opendmb@...il.com, kapil.hali@...adcom.com,
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 devicetree@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: sram: Document reg-io-width property

On 8/13/24 12:29, Rob Herring (Arm) wrote:
> 
> On Tue, 13 Aug 2024 11:07:46 -0700, Florian Fainelli wrote:
>> Some SRAMs need to be accessed with a specific access width, define
>> the 'reg-io-width' property specifying such access sizes.
>>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>> Signed-off-by: Florian Fainelli <florian.fainelli@...adcom.com>
>> ---
>>   Documentation/devicetree/bindings/sram/sram.yaml | 6 ++++++
>>   1 file changed, 6 insertions(+)
>>
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> ./Documentation/devicetree/bindings/sram/sram.yaml:106:12: [warning] wrong indentation: expected 10 but found 11 (indentation)

My bad, I had it corrected on the machine I used to do v1, but did not 
carry that commit over. Will fix in v3.
-- 
Florian