From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 0/4] ARM: dts: at91: calao_usb: fix various naming problems
Date: Tue, 4 Feb 2025 11:43:32 +0100 [thread overview]
Message-ID: <Z6HvVDV0tE99w3od@shikoro> (raw)
In-Reply-To: <173835855390.46028.13185945524234872285.robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 271 bytes --]
> arch/arm/boot/dts/microchip/usb_a9263.dtb: /: failed to match any schema with compatible: ['calao,usb-a9263', 'atmel,at91sam9263', 'atmel,at91sam9']
I forgot to mention there is a dependency. As I need to resend the
dependency anyhow, I will put it into the series.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-04 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 21:02 [PATCH 0/4] ARM: dts: at91: calao_usb: fix various naming problems Wolfram Sang
2025-01-31 21:02 ` [PATCH 1/4] ARM: dts: at91: usb_a9263: fix wrong vendor Wolfram Sang
2025-01-31 21:02 ` [PATCH 2/4] ARM: dts: at91: use correct vendor name for Calao boards Wolfram Sang
2025-01-31 21:02 ` [PATCH 3/4] ARM: dts: at91: calao_usb: fix button nodes Wolfram Sang
2025-01-31 21:02 ` [PATCH 4/4] ARM: dts: at91: usb_a9g20_lpw: use proper mmc node name Wolfram Sang
2025-01-31 21:23 ` [PATCH 0/4] ARM: dts: at91: calao_usb: fix various naming problems Rob Herring (Arm)
2025-02-04 10:43 ` Wolfram Sang [this message]
2025-02-03 13:08 ` Nicolas Ferre
2025-02-17 9:14 ` Claudiu Beznea
2025-02-17 9:53 ` Wolfram Sang
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=Z6HvVDV0tE99w3od@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).