Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [v2][PATCH] net: phy: Don't WARN for PHY_READY state in
 mdio_bus_phy_resume()
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166121821469.29630.864832018240851621.git-patchwork-notify@kernel.org>
Date:   Tue, 23 Aug 2022 01:30:14 +0000
References: <20220819082451.1992102-1-xiaolei.wang@windriver.com>
In-Reply-To: <20220819082451.1992102-1-xiaolei.wang@windriver.com>
To:     Xiaolei Wang <xiaolei.wang@windriver.com>
Cc:     andrew@lunn.ch, hkallweit1@gmail.com, f.fainelli@gmail.com,
        linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
        kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 19 Aug 2022 16:24:51 +0800 you wrote:
> For some MAC drivers, they set the mac_managed_pm to true in its
> ->ndo_open() callback. So before the mac_managed_pm is set to true,
> we still want to leverage the mdio_bus_phy_suspend()/resume() for
> the phy device suspend and resume. In this case, the phy device is
> in PHY_READY, and we shouldn't warn about this. It also seems that
> the check of mac_managed_pm in WARN_ON is redundant since we already
> check this in the entry of mdio_bus_phy_resume(), so drop it.
> 
> [...]

Here is the summary with links:
  - [v2] net: phy: Don't WARN for PHY_READY state in mdio_bus_phy_resume()
    https://git.kernel.org/netdev/net/c/6dbe852c379f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html