From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, pabeni@redhat.com, netdev@vger.kernel.org,
arinc.unal@arinc9.com, linux-mediatek@lists.infradead.org,
daniel@makrotopia.org, Mark-MC.Lee@mediatek.com,
edumazet@google.com, john@phrozen.org,
linux-arm-kernel@lists.infradead.org, sean.wang@mediatek.com,
nbd@nbd.name, matthias.bgg@gmail.com, kuba@kernel.org,
angelogioacchino.delregno@collabora.com, lorenzo@kernel.org,
davem@davemloft.net, dwmw@amazon.co.uk, hkallweit1@gmail.com
Subject: Re: [PATCH net-next v2 0/4] Remove legacy phylink behaviour
Date: Tue, 25 Jul 2023 13:10:22 +0000 [thread overview]
Message-ID: <169029062222.12684.2359979941607233325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZLw8DoRskRXLQK37@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 22 Jul 2023 21:29:02 +0100 you wrote:
> Hi,
>
> This series removes the - as far as I can tell - unreachable code in
> mtk_eth_soc that relies upon legacy phylink behaviour, and then removes
> the support in phylink for this legacy behaviour.
>
> Patch 1 removes the clocking configuration from mtk_eth_soc for non-
> TRGMII, non-serdes based interface modes, and disables those interface
> modes prior to phylink configuration.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] net: ethernet: mtk_eth_soc: remove incorrect PLL configuration
https://git.kernel.org/netdev/net-next/c/76a4cb755cf9
- [net-next,v2,2/4] net: ethernet: mtk_eth_soc: remove mac_pcs_get_state and modernise
https://git.kernel.org/netdev/net-next/c/28e1737d2544
- [net-next,v2,3/4] net: phylink: strip out pre-March 2020 legacy code
https://git.kernel.org/netdev/net-next/c/4d72c3bb60dd
- [net-next,v2,4/4] net: phylink: explicitly invalidate link_state members in mac_config
https://git.kernel.org/netdev/net-next/c/c5714f68a76b
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:[~2023-07-25 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 20:29 [PATCH net-next v2 0/4] Remove legacy phylink behaviour Russell King (Oracle)
2023-07-22 20:32 ` [PATCH net-next v2 1/4] net: ethernet: mtk_eth_soc: remove incorrect PLL configuration Russell King (Oracle)
2023-07-22 20:32 ` [PATCH net-next v2 2/4] net: ethernet: mtk_eth_soc: remove mac_pcs_get_state and modernise Russell King (Oracle)
2023-07-22 20:32 ` [PATCH net-next v2 3/4] net: phylink: strip out pre-March 2020 legacy code Russell King (Oracle)
2023-07-22 20:33 ` [PATCH net-next v2 4/4] net: phylink: explicitly invalidate link_state members in mac_config Russell King (Oracle)
2023-07-25 13:10 ` 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=169029062222.12684.2359979941607233325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.co.uk \
--cc=edumazet@google.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=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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).