netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com,
	hubert.wisniewski.25632@gmail.com, stable@vger.kernel.org,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, lukas@wunner.de, linux@armlinux.org.uk,
	xu.yang_2@nxp.com, linux-usb@vger.kernel.org
Subject: Re: [PATCH net v1 1/1] net: usb: asix: ax88772: drop phylink use in PM to avoid MDIO runtime PM wakeups
Date: Thu, 11 Sep 2025 01:00:07 +0000	[thread overview]
Message-ID: <175755240775.1614523.6238417350387130294.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250908112619.2900723-1-o.rempel@pengutronix.de>

Hello:

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

On Mon,  8 Sep 2025 13:26:19 +0200 you wrote:
> Drop phylink_{suspend,resume}() from ax88772 PM callbacks.
> 
> MDIO bus accesses have their own runtime-PM handling and will try to
> wake the device if it is suspended. Such wake attempts must not happen
> from PM callbacks while the device PM lock is held. Since phylink
> {sus|re}sume may trigger MDIO, it must not be called in PM context.
> 
> [...]

Here is the summary with links:
  - [net,v1,1/1] net: usb: asix: ax88772: drop phylink use in PM to avoid MDIO runtime PM wakeups
    https://git.kernel.org/netdev/net/c/5537a4679403

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



  parent reply	other threads:[~2025-09-11  1:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250911135853eucas1p283b1afd37287b715403cd2cdbfa03a94@eucas1p2.samsung.com>
2025-09-08 11:26 ` [PATCH net v1 1/1] net: usb: asix: ax88772: drop phylink use in PM to avoid MDIO runtime PM wakeups Oleksij Rempel
2025-09-08 17:00   ` Hubert Wiśniewski
2025-09-09  7:17     ` Oleksij Rempel
2025-09-09 23:56       ` Jakub Kicinski
2025-09-10  4:16         ` Oleksij Rempel
2025-09-09  2:05   ` Xu Yang
2025-09-09 23:58   ` Jakub Kicinski
2025-09-10  4:11     ` Oleksij Rempel
2025-09-11  0:50       ` Jakub Kicinski
2025-09-11  1:00   ` patchwork-bot+netdevbpf [this message]
2025-09-11 13:58   ` Marek Szyprowski
2025-09-11 14:39     ` Russell King (Oracle)
2025-09-11 14:55       ` Jakub Kicinski
2025-09-11 20:46         ` Russell King (Oracle)
2025-09-12  2:30           ` Alan Stern
2025-09-12  8:33             ` Russell King (Oracle)
2025-09-12 14:29               ` Alan Stern
2025-09-12 14:37                 ` Russell King (Oracle)
2025-09-13  6:45                   ` Oleksij Rempel
2025-09-16  7:18                     ` Oleksij Rempel
2025-09-16 14:42                       ` Jakub Kicinski

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=175755240775.1614523.6238417350387130294.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hubert.wisniewski.25632@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas@wunner.de \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=xu.yang_2@nxp.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;
as well as URLs for NNTP newsgroup(s).