linux-kernel - Re: [PATCH 0/3] Convert STM32 ROMEM to json-schema

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]

Date:   Thu, 9 Jan 2020 10:01:02 +0100
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Benjamin Gaignard <benjamin.gaignard@...com>,
        <srinivas.kandagatla@...aro.org>, <robh+dt@...nel.org>,
        <mark.rutland@....com>, <mcoquelin.stm32@...il.com>,
        <fabrice.gasnier@...com>
CC:     <devicetree@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Convert STM32 ROMEM to json-schema

Hi Benjamin,

On 12/19/19 3:41 PM, Benjamin Gaignard wrote:
> Convert STM32 ROMEM to json-schema and fix the issues detected on stm32 dtsi
> files.
> Note that stm32mp1 patch should be applied on top of the stm32-next tree.
> 
> Benjamin Gaignard (3):
>    dt-bindings: nvmem: Convert STM32 ROMEM to json-schema
>    ARM: dts: stm32: change nvmem node name on stm32f429
>    ARM: dts: stm32: change nvmem node name on stm32mp1
> 
>   .../devicetree/bindings/nvmem/st,stm32-romem.txt   | 31 ---------------
>   .../devicetree/bindings/nvmem/st,stm32-romem.yaml  | 46 ++++++++++++++++++++++
>   arch/arm/boot/dts/stm32f429.dtsi                   |  2 +-
>   arch/arm/boot/dts/stm32mp151.dtsi                  |  2 +-
>   4 files changed, 48 insertions(+), 33 deletions(-)
>   delete mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.txt
>   create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml
> 

DT patches applied on stm32-next.

Thanks
Alex