From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-arm-kernel@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 0/4] ARM: dts: at91: calao_usb: fix various naming problems
Date: Mon, 17 Feb 2025 11:14:37 +0200 [thread overview]
Message-ID: <7e966eea-e2e7-4fd4-bc6e-67fd49c57ddd@tuxon.dev> (raw)
In-Reply-To: <20250131210236.36212-6-wsa+renesas@sang-engineering.com>
Hi, Wolfram,
> Wolfram Sang (4):
> ARM: dts: at91: usb_a9263: fix wrong vendor
For this, I'll be waiting a follow up on
https://lore.kernel.org/all/20250131162713.33524-2-wsa+renesas@sang-engineering.com/
> ARM: dts: at91: use correct vendor name for Calao boards
> ARM: dts: at91: calao_usb: fix button nodes
> ARM: dts: at91: usb_a9g20_lpw: use proper mmc node name
These were applied to at91-dt, thanks!
next prev parent reply other threads:[~2025-02-17 9:14 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
2025-02-03 13:08 ` Nicolas Ferre
2025-02-17 9:14 ` Claudiu Beznea [this message]
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=7e966eea-e2e7-4fd4-bc6e-67fd49c57ddd@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--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 \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).