linux-kernel - Re: [PATCH v3 1/3] arm64: dts: nuvoton: fix warning and nodes order

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: <9b2be593-8fc6-4089-bbb2-b8c496b1b2a4@kernel.org>
Date: Sun, 19 Oct 2025 18:52:18 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Tomer Maimon <tmaimon77@...il.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 avifishman70@...il.com, tali.perry1@...il.com, joel@....id.au,
 venture@...gle.com, yuenn@...gle.com, benjaminfair@...gle.com,
 openbmc@...ts.ozlabs.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/3] arm64: dts: nuvoton: fix warning and nodes order

On 19/10/2025 16:30, Tomer Maimon wrote:
> Hi Krzysztof,
> 
> Thanks for your comments
> 
> On Sun, 19 Oct 2025 at 13:35, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>
>> On 25/09/2025 22:06, Tomer Maimon wrote:
>>> Fix the warning in the gcr and timer nodes, and modify nodes order by
>>
>> What warning?
> This warning that I got from Andrew mail
> [I] 0 andrew@...hei ~/s/k/l/o/build.arm64.default ((00e2ab2e))> make
> CHECK_DTBS=y nuvoton/nuvoton-npcm845-evb.dtb
>   SCHEMA  Documentation/devicetree/bindings/processed-schema.json
>   DTC [C] arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb
> /home/andrew/src/
> kernel.org/linux/origin/build.arm64.default/arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb:
> / (nuvoton,npcm845-evb): memory@0: 'device_type' is a required property
>         from schema $id: http://devicetree.org/schemas/memory.yaml#


Commit msg should explain that. See git history how to add such
information to the commit msg.

Anyway, all other comments stay valid and I expect improved/different fixes.

You don't sprinkle random compatibles because someone or something told
you, right?

Best regards,
Krzysztof