From: patchwork-bot+netdevbpf@kernel.org
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net: renesas: set 'mac_managed_pm' at probe time
Date: Fri, 17 Mar 2023 00:30:20 +0000 [thread overview]
Message-ID: <167901302021.26766.6629035403026123851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230315074115.3008-1-wsa+renesas@sang-engineering.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Mar 2023 08:41:13 +0100 you wrote:
> When suspending/resuming an interface which was not up, we saw mdiobus
> related PM handling despite 'mac_managed_pm' being set for RAVB/SH_ETH.
> Heiner kindly suggested the fix to set this flag at probe time, not at
> init/open time. I implemented his suggestion and it works fine on these
> two Renesas drivers.
>
> Changes since v1:
> * added tag from Michal (thanks!)
> * split out patches which are for 'net' only (Thanks, Simon!)
>
> [...]
Here is the summary with links:
- [net,v2,1/2] ravb: avoid PHY being resumed when interface is not up
https://git.kernel.org/netdev/net/c/7f5ebf5dae42
- [net,v2,2/2] sh_eth: avoid PHY being resumed when interface is not up
https://git.kernel.org/netdev/net/c/c6be7136afb2
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-17 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 7:41 [PATCH net v2 0/2] net: renesas: set 'mac_managed_pm' at probe time Wolfram Sang
2023-03-15 7:41 ` [PATCH net v2 1/2] ravb: avoid PHY being resumed when interface is not up Wolfram Sang
2023-03-16 19:56 ` Sergey Shtylyov
2023-03-16 20:01 ` Florian Fainelli
2023-03-16 20:06 ` Wolfram Sang
2023-03-16 20:07 ` Florian Fainelli
2023-03-15 7:41 ` [PATCH net v2 2/2] sh_eth: " Wolfram Sang
2023-03-16 19:58 ` Sergey Shtylyov
2023-03-17 0: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=167901302021.26766.6629035403026123851.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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.