From: patchwork-bot+netdevbpf@kernel.org
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch,
florian.fainelli@broadcom.com
Subject: Re: [PATCH net-next v3 0/2] Keep PHY link during WoL sleep cycle
Date: Fri, 08 May 2026 23:50:09 +0000 [thread overview]
Message-ID: <177828420904.900660.8009057314618437924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506213114.2002886-1-justin.chen@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 May 2026 14:31:12 -0700 you wrote:
> First we divide the init/deinit path to allow for a partial init/deinit
> during a sleep cycle. We also remove some unnecessary small functions at
> the same time.
>
> Then we modify the suspend and resume path to allow for a partial bring
> down and bring up. This allow us to keep the PHY link up and to resume
> network traffic much quicker. Note we only do this when WoL is enabled
> since the PHY is already powered. In the non-WoL case we want to follow
> the same flow.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: bcmasp: Divide init to allow partial bring up
https://git.kernel.org/netdev/net-next/c/e97ffa4e975c
- [net-next,v3,2/2] net: bcmasp: Keep phy link during WoL sleep cycle
https://git.kernel.org/netdev/net-next/c/e447b677bb26
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:[~2026-05-08 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 21:31 [PATCH net-next v3 0/2] Keep PHY link during WoL sleep cycle Justin Chen
2026-05-06 21:31 ` [PATCH net-next v3 1/2] net: bcmasp: Divide init to allow partial bring up Justin Chen
2026-05-06 21:31 ` [PATCH net-next v3 2/2] net: bcmasp: Keep phy link during WoL sleep cycle Justin Chen
2026-05-07 20:08 ` Florian Fainelli
2026-05-08 23:50 ` 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=177828420904.900660.8009057314618437924.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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