From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Yang <mmyangfl@gmail.com>, netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next v3 1/3] dt-bindings: net: dsa: yt921x: Add Motorcomm YT921x switch support
Date: Sat, 16 Aug 2025 10:36:19 +0200 [thread overview]
Message-ID: <e389fcf9-5c77-4a3e-a5e4-9076c0aa930f@kernel.org> (raw)
In-Reply-To: <20250816052323.360788-2-mmyangfl@gmail.com>
On 16/08/2025 07:23, David Yang wrote:
> The Motorcomm YT921x series is a family of Ethernet switches with up to
> 8 internal GbE PHYs and up to 2 GMACs.
>
> Signed-off-by: David Yang <mmyangfl@gmail.com>
> ---
> .../bindings/net/dsa/motorcomm,yt921x.yaml | 166 ++++++++++++++++++
Previous version was not tested. This is not tested, either.
You must test your code BEFORE you send it, not after.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-16 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 5:23 [net-next v3 0/3] net: dsa: yt921x: Add support for Motorcomm YT921x David Yang
2025-08-16 5:23 ` [net-next v3 1/3] dt-bindings: net: dsa: yt921x: Add Motorcomm YT921x switch support David Yang
2025-08-16 6:36 ` Rob Herring (Arm)
2025-08-16 8:36 ` Krzysztof Kozlowski [this message]
2025-08-16 15:11 ` Andrew Lunn
2025-08-16 5:23 ` [net-next v3 2/3] net: dsa: tag_yt921x: add support for Motorcomm YT921x tags David Yang
2025-08-16 15:24 ` Andrew Lunn
2025-08-16 5:23 ` [net-next v3 3/3] net: dsa: yt921x: Add support for Motorcomm YT921x David Yang
2025-08-16 15:29 ` Andrew Lunn
2025-08-16 15:20 ` [net-next v3 0/3] " Andrew Lunn
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=e389fcf9-5c77-4a3e-a5e4-9076c0aa930f@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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).