linux-kernel - Re: [GIT PULL] ARM: at91: dt for 5.13

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 for Android: free password hash cracker in your pocket

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

Message-ID: <71b2bd27-0d3b-3331-4f79-85b22594e20b@microchip.com>
Date:   Thu, 8 Apr 2021 18:34:37 +0200
From:   Nicolas Ferre <nicolas.ferre@...rochip.com>
To:     Arnd Bergmann <arnd@...nel.org>, <soc@...nel.org>,
        Olof Johansson <olof@...om.net>, <arm@...nel.org>
CC:     Arnd Bergmann <arnd@...db.de>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>,
        Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] ARM: at91: dt for 5.13

Hi Arnd,

On 08/04/2021 at 17:24, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
> 
> On Wed, 7 Apr 2021 13:44:15 +0200, nicolas.ferre@...rochip.com wrote:
>> Arnd, Olof,
>>
>> Here is first batch of dt changes for 5.13. Please pull.
>>
>> Thanks, best regards,
>>    Nicolas
>>
>> The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
>>
>> [...]
> 
> Merged into arm/dt, thanks!
> 
> I saw two new warnings from 'make dtbs_check W=1':
> 
> arch/arm/boot/dts/at91-sama5d2_ptc_ek.dt.yaml: /: 'etm@...000' does not match any of the regexes: '@(0|[1-9a-f][0-9a-f]*)$', '^[^@]+$', 'pinctrl-[0-9]+'
> arch/arm/boot/dts/at91-kizbox3-hs.dt.yaml: /: 'etm@...000' does not match any of the regexes: '@(0|[1-9a-f][0-9a-f]*)$', '^[^@]+$', 'pinctrl-[0-9]+'

Oh, got it: it's the upper case letter withing the etm hex address. I 
used this one to mach what was done in the reg property. I'm fixing both 
of them and sending the patch to the ml right now.

Tell me if I add it to a subsequent pull-request or if you prefer to 
take it the soonest in order to not generate additional warnings upstream.

BTW, I now have a dtschema at the proper level of support for running 
"make dtbs_check W=1" and will do it before sending pull-requests in the 
future.

Thanks for the heads-up. Best regards,
   Nicolas

> 
> merge commit: e2b064fec8e49112f7dac779fcec12ded40728c2
> 
>         Arnd
> 


-- 
Nicolas Ferre