From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
hkallweit1@gmail.com, linux@armlinux.org.uk,
sean.anderson@seco.com, colin.foster@in-advantage.com,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH v2 net-next 0/4] Remove phylink_validate() from Felix DSA driver
Date: Wed, 16 Nov 2022 05:00:19 +0000 [thread overview]
Message-ID: <166857481979.8148.8505709877128649985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114170730.2189282-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Nov 2022 19:07:26 +0200 you wrote:
> v1->v2: leave dsa_port_phylink_validate() for now, just remove
> ds->ops->phylink_validate()
>
> The Felix DSA driver still uses its own phylink_validate() procedure
> rather than the (relatively newly introduced) phylink_generic_validate()
> because the latter did not cater for the case where a PHY provides rate
> matching between the Ethernet cable side speed and the SERDES side
> speed (and does not advertise other speeds except for the SERDES speed).
>
> [...]
Here is the summary with links:
- [v2,net-next,1/4] net: phy: aquantia: add AQR112 and AQR412 PHY IDs
https://git.kernel.org/netdev/net-next/c/973fbe68df39
- [v2,net-next,2/4] net: dsa: felix: use phylink_generic_validate()
https://git.kernel.org/netdev/net-next/c/3e7e783291b4
- [v2,net-next,3/4] net: mscc: ocelot: drop workaround for forcing RX flow control
https://git.kernel.org/netdev/net-next/c/de8586ed4311
- [v2,net-next,4/4] net: dsa: remove phylink_validate() method
https://git.kernel.org/netdev/net-next/c/53d04b981110
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-16 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 17:07 [PATCH v2 net-next 0/4] Remove phylink_validate() from Felix DSA driver Vladimir Oltean
2022-11-14 17:07 ` [PATCH v2 net-next 1/4] net: phy: aquantia: add AQR112 and AQR412 PHY IDs Vladimir Oltean
2022-11-14 17:07 ` [PATCH v2 net-next 2/4] net: dsa: felix: use phylink_generic_validate() Vladimir Oltean
2022-11-14 17:09 ` Russell King (Oracle)
2022-11-14 17:07 ` [PATCH v2 net-next 3/4] net: mscc: ocelot: drop workaround for forcing RX flow control Vladimir Oltean
2022-11-14 17:10 ` Russell King (Oracle)
2022-11-14 17:07 ` [PATCH v2 net-next 4/4] net: dsa: remove phylink_validate() method Vladimir Oltean
2022-11-14 17:11 ` Russell King (Oracle)
2022-11-16 5:00 ` patchwork-bot+netdevbpf [this message]
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=166857481979.8148.8505709877128649985.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.com \
--cc=vladimir.oltean@nxp.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).