From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
alexandre.torgue@foss.st.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, joabreu@synopsys.com,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com, madalin.bucur@nxp.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, sean.anderson@seco.com, ahalaney@redhat.com,
fancer.lancer@gmail.com
Subject: Re: [PATCH net-next 0/6] net: phylink: rearrange ovr_an_inband support
Date: Fri, 31 May 2024 01:40:32 +0000 [thread overview]
Message-ID: <171711963296.18580.14971727622513760852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZlctinnTT8Xhemsm@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 May 2024 14:28:42 +0100 you wrote:
> Hi,
>
> This series addresses the use of the ovr_an_inband flag, which is used
> by two drivers to indicate to phylink that they wish to use inband mode
> without firmware specifying inband mode.
>
> The issue with ovr_an_inband is that it overrides not only PHY mode,
> but also fixed-link mode. Both of the drivers that set this flag
> contain code to detect when fixed-link mode will be used, and then
> either avoid setting it or explicitly clear the flag. This is
> wasteful when phylink already knows this.
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: phylink: rearrange phylink_parse_mode()
https://git.kernel.org/netdev/net-next/c/75518b0dc9d6
- [net-next,2/6] net: phylink: move test for ovr_an_inband
https://git.kernel.org/netdev/net-next/c/fea49f065c1c
- [net-next,3/6] net: phylink: rename ovr_an_inband to default_an_inband
https://git.kernel.org/netdev/net-next/c/02d00dc73d8d
- [net-next,4/6] net: fman_memac: remove the now unnecessary checking for fixed-link
https://git.kernel.org/netdev/net-next/c/5e332954e760
- [net-next,5/6] net: stmmac: rename xpcs_an_inband to default_an_inband
https://git.kernel.org/netdev/net-next/c/83f55b01dd90
- [net-next,6/6] net: stmmac: dwmac-intel: remove checking for fixed link
https://git.kernel.org/netdev/net-next/c/ab77c7aa9388
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-31 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 13:28 [PATCH net-next 0/6] net: phylink: rearrange ovr_an_inband support Russell King (Oracle)
2024-05-29 13:29 ` [PATCH net-next 3/6] net: phylink: rename ovr_an_inband to default_an_inband Russell King (Oracle)
2024-05-29 13:29 ` [PATCH net-next 5/6] net: stmmac: rename xpcs_an_inband " Russell King (Oracle)
2024-05-29 13:29 ` [PATCH net-next 6/6] net: stmmac: dwmac-intel: remove checking for fixed link Russell King (Oracle)
2024-05-29 22:02 ` [PATCH net-next 0/6] net: phylink: rearrange ovr_an_inband support Andrew Halaney
2024-05-31 1:40 ` 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=171711963296.18580.14971727622513760852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahalaney@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=madalin.bucur@nxp.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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).