From: patchwork-bot+netdevbpf@kernel.org
To: Pavithra Sathyanarayanan <Pavithra.Sathyanarayanan@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bryan.whitehead@microchip.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next v1] net: microchip: lan743x: add fixed phy unregister support
Date: Sun, 17 Sep 2023 11:00:27 +0000 [thread overview]
Message-ID: <169494842740.21621.7514600997922629086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230914061737.3147-1-Pavithra.Sathyanarayanan@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 14 Sep 2023 11:47:37 +0530 you wrote:
> When operating in fixed phy mode and if there is repeated open/close
> phy test cases, everytime the fixed phy is registered as a new phy
> which leads to overrun after 32 iterations. It is solved by adding
> fixed_phy_unregister() in the phy_close path.
>
> In phy_close path, netdev->phydev cannot be used directly in
> fixed_phy_unregister() due to two reasons,
> - netdev->phydev is set to NULL in phy_disconnect()
> - fixed_phy_unregister() can be called only after phy_disconnect()
> So saving the netdev->phydev in local variable 'phydev' and
> passing it to phy_disconnect().
>
> [...]
Here is the summary with links:
- [net-next,v1] net: microchip: lan743x: add fixed phy unregister support
https://git.kernel.org/netdev/net-next/c/1e73cfe85952
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-09-17 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 6:17 [PATCH net-next v1] net: microchip: lan743x: add fixed phy unregister support Pavithra Sathyanarayanan
2023-09-17 11: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=169494842740.21621.7514600997922629086.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Pavithra.Sathyanarayanan@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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