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] [day] [month] [year] [list]
Message-ID: <1e713377-c5e0-fc4f-3f32-d35be4367091@foss.st.com>
Date:   Mon, 25 Jan 2021 14:22:03 +0100
From:   "gabriel.fernandez@...s.st.com" <gabriel.fernandez@...s.st.com>
To:     Rob Herring <robh@...nel.org>
CC:     Stephen Boyd <sboyd@...nel.org>, <linux-clk@...r.kernel.org>,
        Alexandre Torgue <alexandre.torgue@...com>,
        Rob Herring <robh+dt@...nel.org>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Etienne Carriere <etienne.carriere@...com>,
        <devicetree@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>,
        Michael Turquette <mturquette@...libre.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 13/14] dt-bindings: clock: stm32mp1 new compatible for
 secure rcc

Hi Rob,

many thanks i will send a v2.

Best regards

Gabriel

On 1/22/21 3:00 PM, Rob Herring wrote:
> On Fri, 22 Jan 2021 11:51:00 +0100, gabriel.fernandez@...s.st.com wrote:
>> From: Gabriel Fernandez <gabriel.fernandez@...s.st.com>
>>
>> Introduce new compatible string "st,stm32mp1-rcc-secure" for
>> stm32mp1 clock driver when the device is configured with RCC
>> security support hardened.
>>
>> Signed-off-by: Etienne Carriere <etienne.carriere@...com>
>> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@...s.st.com>
>> ---
>>   Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.example.dt.yaml: rcc@...00000: compatible:1: 'st,stm32mp1-rcc' was expected
> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.example.dt.yaml: rcc@...00000: compatible: ['st,stm32mp1-rcc-secure', 'syscon'] is too short
> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
>
> See https://patchwork.ozlabs.org/patch/1430316
>
> This check can fail if there are any dependencies. The base for a patch
> series is generally the most recent rc1.
>
> If you already ran 'make dt_binding_check' and didn't see the above
> error(s), then make sure 'yamllint' is installed and dt-schema is up to
> date:
>
> pip3 install dtschema --upgrade
>
> Please check and re-submit.
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ