From: Conor Dooley <conor@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>, Imre Kaloz <kaloz@openwrt.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] dt-bindings: arm: List actiontec devices
Date: Thu, 14 Aug 2025 21:46:03 +0100 [thread overview]
Message-ID: <20250814-goliath-exfoliate-e4d36c37751e@spud> (raw)
In-Reply-To: <20250814-ixp4xx-mi424wr-dts-v1-2-b7c10f3c4193@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Thu, Aug 14, 2025 at 06:40:04PM +0200, Linus Walleij wrote:
> One two IXP4xx device families from OpenWrts backlog:
> Actiontec MI424WR revision A/C and revision D, both
> of these are IXP4xx devices.
>
> Revisions E and later use different chipsets.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-14 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 16:40 [PATCH 0/3] ARM: dts: ixp4xx: Add device trees for MI424WR Linus Walleij
2025-08-14 16:40 ` [PATCH 1/3] dt-bindings: Add Actiontec vendor prefix Linus Walleij
2025-08-14 20:46 ` Conor Dooley
2025-08-14 16:40 ` [PATCH 2/3] dt-bindings: arm: List actiontec devices Linus Walleij
2025-08-14 20:46 ` Conor Dooley [this message]
2025-08-14 21:03 ` Rob Herring
2025-08-14 21:04 ` Rob Herring
2025-08-14 16:40 ` [PATCH 3/3] ARM: dts: Add ixp4xx Actiontec MI424WR device trees Linus Walleij
2025-08-14 21:13 ` Florian Fainelli
2025-08-15 9:09 ` Linus Walleij
2025-08-15 21:19 ` [PATCH 0/3] ARM: dts: ixp4xx: Add device trees for MI424WR Rob Herring (Arm)
2025-08-19 13:14 ` Linus Walleij
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=20250814-goliath-exfoliate-e4d36c37751e@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaloz@openwrt.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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