Re: [PATCH 0/3] ARM: dts: ti: omap: fix dtbs_check warnings for ti,gpmc-nand and ti,gpmc-onenend

From: Kevin Hilman
Date: Fri Oct 04 2024 - 17:01:48 EST


Hi Roger,

Roger Quadros <rogerq@xxxxxxxxxx> writes:

> This series fixes dtbs_check warnings on OMAP platforms
> for ti,gpmc-nand and ti,gpmc-onenand.
>
> The following warnings are fixed
> - "nand@0,0: Unevaluated properties are not allowed ('linux,mtd-name' was unexpected)"
> - "nand@0,0: Unevaluated properties are not allowed ('gpmc,device-nand' was unexpected)"
> - "omap3430-sdp.dtb: onenand@2,0: Unevaluated properties are not allowed ('linux,mtd-name' was unexpected)"
>
> ---
> Roger Quadros (3):
> ARM: dts: ti: drop linux,mtd-name from NAND nodes
> ARM: dts: ti: omap: am335x-baltos: drop "gpmc,device-nand" from NAND node
> ARM: dts: ti: omap3434-sdp: drop linux,mtd-name from onenand node
>
> arch/arm/boot/dts/ti/omap/am335x-baltos.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/am3517-som.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/dm8148-evm.dts | 1 -
> arch/arm/boot/dts/ti/omap/dm8168-evm.dts | 1 -
> arch/arm/boot/dts/ti/omap/dra62x-j5eco-evm.dts | 1 -
> arch/arm/boot/dts/ti/omap/logicpd-som-lv.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/logicpd-torpedo-som.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/omap3-evm-37xx.dts | 1 -
> arch/arm/boot/dts/ti/omap/omap3-evm.dts | 1 -
> arch/arm/boot/dts/ti/omap/omap3-igep.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/omap3-ldp.dts | 1 -
> arch/arm/boot/dts/ti/omap/omap3-overo-base.dtsi | 1 -
> arch/arm/boot/dts/ti/omap/omap3430-sdp.dts | 2 --
> 13 files changed, 14 deletions(-)
> ---
> base-commit: 5be63fc19fcaa4c236b307420483578a56986a37
> change-id: 20240830-gpmc-dtb-de2ce28acfb6

FYI: you seem to have used the same change-id in this series as in a
previous patch[1], which means when I point b4 at this series, notices
the same change-id in the other patch, thinks it's a v2 of this series,
and tries to apply the v2 patch instead.

I was able to "encourage" b4 to apply this series by using -v1, but it
took me a bit to figure out why I pointed it at a 3 patch series and it
was applying a single patch from a different thread.

Kevin

[1] https://lore.kernel.org/all/20240903-gpmc-dtb-v2-1-8046c1915b96@xxxxxxxxxx/