From: patchwork-bot+netdevbpf@kernel.org
To: Lukas Wunner <lukas@wunner.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
m.szyprowski@samsung.com, f.fainelli@gmail.com,
xiaolei.wang@windriver.com
Subject: Re: [PATCH net] net: phy: Don't WARN for PHY_UP state in mdio_bus_phy_resume()
Date: Tue, 27 Sep 2022 09:00:16 +0000 [thread overview]
Message-ID: <166426921631.22762.7317829989157057472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8128fdb51eeebc9efbf3776a4097363a1317aaf1.1663905575.git.lukas@wunner.de>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Sep 2022 06:09:52 +0200 you wrote:
> Commit 744d23c71af3 ("net: phy: Warn about incorrect mdio_bus_phy_resume()
> state") introduced a WARN() on resume from system sleep if a PHY is not
> in PHY_HALTED state.
>
> Commit 6dbe852c379f ("net: phy: Don't WARN for PHY_READY state in
> mdio_bus_phy_resume()") added an exemption for PHY_READY state from
> the WARN().
>
> [...]
Here is the summary with links:
- [net] net: phy: Don't WARN for PHY_UP state in mdio_bus_phy_resume()
https://git.kernel.org/netdev/net/c/ea64cdfad124
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:[~2022-09-27 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 4:09 [PATCH net] net: phy: Don't WARN for PHY_UP state in mdio_bus_phy_resume() Lukas Wunner
2022-09-27 9: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=166426921631.22762.7317829989157057472.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@armlinux.org.uk \
--cc=lukas@wunner.de \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolei.wang@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.