From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: phy: Ensure state transitions are processed from phy_stop()
Date: Sun, 19 Mar 2023 10:50:18 +0000 [thread overview]
Message-ID: <167922301888.22899.1199680876721811339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230316203325.2026217-1-f.fainelli@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 16 Mar 2023 13:33:24 -0700 you wrote:
> In the phy_disconnect() -> phy_stop() path, we will be forcibly setting
> the PHY state machine to PHY_HALTED. This invalidates the old_state !=
> phydev->state condition in phy_state_machine() such that we will neither
> display the state change for debugging, nor will we invoke the
> link_change_notify() callback.
>
> Factor the code by introducing phy_process_state_change(), and ensure
> that we process the state change from phy_stop() as well.
>
> [...]
Here is the summary with links:
- [net] net: phy: Ensure state transitions are processed from phy_stop()
https://git.kernel.org/netdev/net/c/4203d84032e2
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-19 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 20:33 [PATCH net] net: phy: Ensure state transitions are processed from phy_stop() Florian Fainelli
2023-03-19 10:50 ` 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=167922301888.22899.1199680876721811339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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