public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	Javier Martinez Canillas <javier@dowhile0.org>
Cc: Nishanth Menon <nm@ti.com>,
	srk@ti.com, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH 0/3] ARM: dts: ti: omap: fix dtbs_check warnings for ti,gpmc-nand and ti,gpmc-onenend
Date: Fri, 04 Oct 2024 14:01:32 -0700	[thread overview]
Message-ID: <7ha5fjk2fn.fsf@baylibre.com> (raw)
In-Reply-To: <20240903-gpmc-dtb-v1-0-380952952e34@kernel.org>

Hi Roger,

Roger Quadros <rogerq@kernel.org> 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@kernel.org/


  parent reply	other threads:[~2024-10-04 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 16:43 [PATCH 0/3] ARM: dts: ti: omap: fix dtbs_check warnings for ti,gpmc-nand and ti,gpmc-onenend Roger Quadros
2024-09-03 16:43 ` [PATCH 1/3] ARM: dts: ti: drop linux,mtd-name from NAND nodes Roger Quadros
2024-09-03 16:43 ` [PATCH 2/3] ARM: dts: ti: omap: am335x-baltos: drop "gpmc,device-nand" from NAND node Roger Quadros
2024-09-03 16:43 ` [PATCH 3/3] ARM: dts: ti: omap3434-sdp: drop linux,mtd-name from onenand node Roger Quadros
2024-10-04 21:01 ` Kevin Hilman [this message]
2024-10-04 21:33 ` [PATCH 0/3] ARM: dts: ti: omap: fix dtbs_check warnings for ti,gpmc-nand and ti,gpmc-onenend Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ha5fjk2fn.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eballetbo@gmail.com \
    --cc=javier@dowhile0.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=srk@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox