From: patchwork-bot+netdevbpf@kernel.org
To: John Ernberg <john.ernberg@actia.se>
Cc: wei.fang@nxp.com, shenwei.wang@nxp.com, xiaoning.wang@nxp.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hkallweit1@gmail.com, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
f.fainelli@gmail.com, linux@armlinux.org.uk,
maxime.chevallier@bootlin.com
Subject: Re: [PATCH net v4 0/1] net: fec: Fix to suspend / resume with mac_managed_pm
Date: Thu, 04 Apr 2024 02:30:29 +0000 [thread overview]
Message-ID: <171219782966.25056.2083186308558278938.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240328155909.59613-1-john.ernberg@actia.se>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 Mar 2024 15:59:29 +0000 you wrote:
> Since the introduction of mac_managed_pm in the FEC driver there were some
> discrepancies regarding power management of the PHY.
>
> This failed on our board that has a permanently powered Microchip LAN8700R
> attached to the FEC. Although the root cause of the failure can be traced
> back to f166f890c8f0 ("net: ethernet: fec: Replace interrupt driven MDIO
> with polled IO") and probably even before that, we only started noticing
> the problem going from 5.10 to 6.1.
>
> [...]
Here is the summary with links:
- [v4,1/1] net: fec: Set mac_managed_pm during probe
https://git.kernel.org/netdev/net/c/cbc17e7802f5
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:[~2024-04-04 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 15:59 [PATCH net v4 0/1] net: fec: Fix to suspend / resume with mac_managed_pm John Ernberg
2024-03-28 15:59 ` [PATCH v4 1/1] net: fec: Set mac_managed_pm during probe John Ernberg
2024-04-04 2:30 ` 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=171219782966.25056.2083186308558278938.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=imx@lists.linux.dev \
--cc=john.ernberg@actia.se \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@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