linux-kernel - Re: [PATCH v2 01/19] include: dt-bindings: add LAN969x clock bindings

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: <176589052274.1815136.7513475493879599819.robh@kernel.org>
Date: Tue, 16 Dec 2025 07:11:49 -0600
From: Rob Herring <robh@...nel.org>
To: Robert Marko <robert.marko@...tura.hr>
Cc: netdev@...r.kernel.org, linusw@...nel.org, vkoul@...nel.org, 
 pabeni@...hat.com, jirislaby@...nel.org, lars.povlsen@...rochip.com, 
 linux-arm-kernel@...ts.infradead.org, claudiu.beznea@...on.dev, 
 kuba@...nel.org, mturquette@...libre.com, Steen.Hegelund@...rochip.com, 
 mwalle@...nel.org, tudor.ambarus@...aro.org, devicetree@...r.kernel.org, 
 UNGLinuxDriver@...rochip.com, edumazet@...gle.com, 
 linux-clk@...r.kernel.org, andi.shyti@...nel.org, olivia@...enic.com, 
 conor+dt@...nel.org, luka.perkov@...tura.hr, richard.genoud@...tlin.com, 
 linux-hwmon@...r.kernel.org, krzk+dt@...nel.org, 
 wsa+renesas@...g-engineering.com, Ryan.Wanner@...rochip.com, 
 linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, 
 alexandre.belloni@...tlin.com, lee@...nel.org, linux@...ck-us.net, 
 davem@...emloft.net, gregkh@...uxfoundation.org, 
 kavyasree.kotagiri@...rochip.com, nicolas.ferre@...rochip.com, 
 andrew+netdev@...n.ch, romain.sioen@...rochip.com, sboyd@...nel.org, 
 linux-gpio@...r.kernel.org, linux-spi@...r.kernel.org, 
 linux-serial@...r.kernel.org, daniel.machon@...rochip.com, 
 dmaengine@...r.kernel.org, richardcochran@...il.com, 
 herbert@...dor.apana.org.au, charan.pedumuru@...rochip.com, 
 linux-crypto@...r.kernel.org, linux-i2c@...r.kernel.org, 
 radu_nicolae.pirea@....ro
Subject: Re: [PATCH v2 01/19] include: dt-bindings: add LAN969x clock
 bindings


On Mon, 15 Dec 2025 17:35:18 +0100, Robert Marko wrote:
> Add the required LAN969x clock bindings.
> 
> Signed-off-by: Robert Marko <robert.marko@...tura.hr>
> ---
> Changes in v2:
> * Rename file to microchip,lan9691.h
> 
>  include/dt-bindings/clock/microchip,lan9691.h | 24 +++++++++++++++++++
>  1 file changed, 24 insertions(+)
>  create mode 100644 include/dt-bindings/clock/microchip,lan9691.h
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/next-20251215 (best guess, 14/15 blobs matched)
 Base: tags/next-20251215 (use --merge-base to override)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/microchip/' for 20251215163820.1584926-1-robert.marko@...tura.hr:

arch/arm64/boot/dts/microchip/sparx5_pcb135_emmc.dtb: / (microchip,sparx5-pcb135): compatible: ['microchip,sparx5-pcb135', 'microchip,sparx5'] is valid under each of {'items': [{'const': 'microchip,sparx5-pcb135'}, {'const': 'microchip,sparx5'}], 'maxItems': 2, 'minItems': 2, 'type': 'array'}, {}
	from schema $id: http://devicetree.org/schemas/arm/microchip.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135.dtb: / (microchip,sparx5-pcb135): compatible: ['microchip,sparx5-pcb135', 'microchip,sparx5'] is valid under each of {'items': [{'const': 'microchip,sparx5-pcb135'}, {'const': 'microchip,sparx5'}], 'maxItems': 2, 'minItems': 2, 'type': 'array'}, {}
	from schema $id: http://devicetree.org/schemas/arm/microchip.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134.dtb: / (microchip,sparx5-pcb134): compatible: ['microchip,sparx5-pcb134', 'microchip,sparx5'] is valid under each of {'items': [{'const': 'microchip,sparx5-pcb134'}, {'const': 'microchip,sparx5'}], 'maxItems': 2, 'minItems': 2, 'type': 'array'}, {}
	from schema $id: http://devicetree.org/schemas/arm/microchip.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134_emmc.dtb: / (microchip,sparx5-pcb134): compatible: ['microchip,sparx5-pcb134', 'microchip,sparx5'] is valid under each of {'items': [{'const': 'microchip,sparx5-pcb134'}, {'const': 'microchip,sparx5'}], 'maxItems': 2, 'minItems': 2, 'type': 'array'}, {}
	from schema $id: http://devicetree.org/schemas/arm/microchip.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb125.dtb: / (microchip,sparx5-pcb125): compatible: ['microchip,sparx5-pcb125', 'microchip,sparx5'] is valid under each of {'items': [{'const': 'microchip,sparx5-pcb125'}, {'const': 'microchip,sparx5'}], 'maxItems': 2, 'minItems': 2, 'type': 'array'}, {}
	from schema $id: http://devicetree.org/schemas/arm/microchip.yaml