From: Florian Fainelli <f.fainelli@gmail.com>
To: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>
Cc: UNGLinuxDriver@microchip.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/4] net: dsa: ksz_common: provide own phylink MAC operations
Date: Fri, 26 Apr 2024 11:28:28 -0700 [thread overview]
Message-ID: <962a74ed-9a23-4e56-ae61-d56ecd2ac7b8@gmail.com> (raw)
In-Reply-To: <E1s0O7H-009gpq-IF@rmk-PC.armlinux.org.uk>
On 4/26/24 09:08, Russell King (Oracle) wrote:
> Convert ksz_common to provide its own phylink MAC operations, thus
> avoiding the shim layer in DSA's port.c
>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2024-04-26 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 16:02 [PATCH net-next 0/4] net: dsa: microchip: use phylink_mac_ops for ksz driver Russell King (Oracle)
2024-04-26 16:07 ` [PATCH net-next 1/4] net: dsa: ksz_common: remove phylink_mac_config from ksz_dev_ops Russell King (Oracle)
2024-04-26 18:28 ` Florian Fainelli
2024-04-26 16:08 ` [PATCH net-next 2/4] net: dsa: ksz_common: provide own phylink MAC operations Russell King (Oracle)
2024-04-26 18:28 ` Florian Fainelli [this message]
2024-04-26 16:08 ` [PATCH net-next 3/4] net: dsa: ksz_common: sub-driver phylink ops Russell King (Oracle)
2024-04-26 16:08 ` [PATCH net-next 4/4] net: dsa: ksz_common: use separate phylink_mac_ops for ksz8830 Russell King (Oracle)
2024-04-30 2:20 ` [PATCH net-next 0/4] net: dsa: microchip: use phylink_mac_ops for ksz driver patchwork-bot+netdevbpf
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=962a74ed-9a23-4e56-ae61-d56ecd2ac7b8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--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).