From: Paolo Abeni <pabeni@redhat.com>
To: Tristram.Ha@microchip.com,
Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, devicetree@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Rob Herring <robh@kernel.org>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Marek Vasut <marex@denx.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/2] net: dsa: microchip: Add KSZ8895/KSZ8864 switch support
Date: Tue, 20 Aug 2024 12:08:02 +0200 [thread overview]
Message-ID: <9bd573ff-af83-4f93-a591-aab541d9faac@redhat.com> (raw)
In-Reply-To: <20240815022014.55275-3-Tristram.Ha@microchip.com>
On 8/15/24 04:20, Tristram.Ha@microchip.com wrote:
> From: Tristram Ha <tristram.ha@microchip.com>
>
> KSZ8895/KSZ8864 is a switch family between KSZ8863/73 and KSZ8795, so it
> shares some registers and functions in those switches already
> implemented in the KSZ DSA driver.
>
> Signed-off-by: Tristram Ha <tristram.ha@microchip.com>
I usually wait for an explicit ack from the DSA crew on this kind of
patches, but this one and it really looks really unlikely to indroduce
any regression for the already supported chips and it's lingering since
a bit, so I'm applying it now.
Thanks,
Paolo
next prev parent reply other threads:[~2024-08-20 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 2:20 [PATCH net-next v4 0/2] net: dsa: microchip: Add KSZ8895/KSZ8864 switch support Tristram.Ha
2024-08-15 2:20 ` [PATCH net-next v4 1/2] dt-bindings: " Tristram.Ha
2024-08-15 2:20 ` [PATCH net-next v4 2/2] " Tristram.Ha
2024-08-20 10:08 ` Paolo Abeni [this message]
2024-08-20 10:15 ` Paolo Abeni
2024-08-21 11:02 ` vtpieter
2024-08-22 23:30 ` Tristram.Ha
2024-08-22 23:33 ` Tristram.Ha
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=9bd573ff-af83-4f93-a591-aab541d9faac@redhat.com \
--to=pabeni@redhat.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=woojung.huh@microchip.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).