From: patchwork-bot+netdevbpf@kernel.org
To: Michael Sit Wei Hong <michael.wei.hong.sit@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
boon.leong.ong@intel.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
hkallweit1@gmail.com, andrew@lunn.ch, hong.aun.looi@intel.com,
weifeng.voon@intel.com, peter.jun.ann.lai@intel.com
Subject: Re: [PATCH net v5 0/3] Fix PHY handle no longer parsing
Date: Fri, 31 Mar 2023 08:30:18 +0000 [thread overview]
Message-ID: <168025141828.29195.16930878780114551946.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230330091404.3293431-1-michael.wei.hong.sit@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 30 Mar 2023 17:14:01 +0800 you wrote:
> After the fixed link support was introduced, it is observed that PHY
> no longer attach to the MAC properly. So we introduce a helper
> function to determine if the MAC should expect to connect to a PHY
> and proceed accordingly.
>
> Michael Sit Wei Hong (3):
> net: phylink: add phylink_expects_phy() method
> net: stmmac: check if MAC needs to attach to a PHY
> net: stmmac: remove redundant fixup to support fixed-link mode
>
> [...]
Here is the summary with links:
- [net,v5,1/3] net: phylink: add phylink_expects_phy() method
https://git.kernel.org/netdev/net/c/653a180957a8
- [net,v5,2/3] net: stmmac: check if MAC needs to attach to a PHY
https://git.kernel.org/netdev/net/c/fe2cfbc96803
- [net,v5,3/3] net: stmmac: remove redundant fixup to support fixed-link mode
https://git.kernel.org/netdev/net/c/6fc21a6ed595
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-03-31 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:14 [PATCH net v5 0/3] Fix PHY handle no longer parsing Michael Sit Wei Hong
2023-03-30 9:14 ` [PATCH net v5 1/3] net: phylink: add phylink_expects_phy() method Michael Sit Wei Hong
2023-04-12 8:38 ` Maxime Chevallier
2023-04-12 6:58 ` Sit, Michael Wei Hong
2023-03-30 9:14 ` [PATCH net v5 2/3] net: stmmac: check if MAC needs to attach to a PHY Michael Sit Wei Hong
2023-04-03 21:24 ` RE " Martin Blumenstingl
2023-04-05 8:48 ` Shahab Vahedi
2023-04-05 9:06 ` Shahab Vahedi
2023-03-30 9:14 ` [PATCH net v5 3/3] net: stmmac: remove redundant fixup to support fixed-link mode Michael Sit Wei Hong
2023-03-31 8:30 ` 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=168025141828.29195.16930878780114551946.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=hong.aun.looi@intel.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=peter.jun.ann.lai@intel.com \
--cc=weifeng.voon@intel.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