From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: chris.snook@gmail.com, nbd@nbd.name, f.fainelli@gmail.com,
john@phrozen.org, Mark-MC.Lee@mediatek.com,
matthias.bgg@gmail.com, sean.wang@mediatek.com,
vivien.didelot@gmail.com, olteanv@gmail.com, andrew@lunn.ch,
davem@davemloft.net, hkallweit1@gmail.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] net: phylink: introduce legacy mode flag
Date: Thu, 09 Dec 2021 20:00:11 +0000 [thread overview]
Message-ID: <163908001132.24516.13773473862700421452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Ya+DGaGmGgWrlVkW@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Dec 2021 15:51:53 +0000 you wrote:
> Hi all,
>
> In March 2020, phylink gained support to split the PCS support out of
> the MAC callbacks. By doing so, a slight behavioural difference was
> introduced when a PCS is present, specifically:
>
> 1) the call to mac_config() when the link comes up or advertisement
> changes were eliminated
> 2) mac_an_restart() will never be called
> 3) mac_pcs_get_state() will never be called
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: phylink: add legacy_pre_march2020 indicator
https://git.kernel.org/netdev/net-next/c/3e5b1feccea7
- [net-next,2/5] net: dsa: mark DSA phylink as legacy_pre_march2020
https://git.kernel.org/netdev/net-next/c/0a9f0794d9bd
- [net-next,3/5] net: mtk_eth_soc: mark as a legacy_pre_march2020 driver
https://git.kernel.org/netdev/net-next/c/b06515367fac
- [net-next,4/5] net: phylink: use legacy_pre_march2020
https://git.kernel.org/netdev/net-next/c/001f4261fe4d
- [net-next,5/5] net: ag71xx: remove unnecessary legacy methods
https://git.kernel.org/netdev/net-next/c/11053047a4af
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:[~2021-12-09 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 15:51 [PATCH net-next 0/5] net: phylink: introduce legacy mode flag Russell King (Oracle)
2021-12-09 13:11 ` [PATCH net-next 1/5] net: phylink: add legacy_pre_march2020 indicator Russell King (Oracle)
2021-12-09 13:11 ` [PATCH net-next 2/5] net: dsa: mark DSA phylink as legacy_pre_march2020 Russell King (Oracle)
2021-12-09 13:11 ` [PATCH net-next 3/5] net: mtk_eth_soc: mark as a legacy_pre_march2020 driver Russell King (Oracle)
2021-12-09 13:11 ` [PATCH net-next 4/5] net: phylink: use legacy_pre_march2020 Russell King (Oracle)
2021-12-09 13:11 ` [PATCH net-next 5/5] net: ag71xx: remove unnecessary legacy methods Russell King (Oracle)
2021-12-09 20: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=163908001132.24516.13773473862700421452.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@gmail.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).