From: patchwork-bot+netdevbpf@kernel.org
To: Eric Work <work.eric@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, irusskikh@marvell.com,
mstarovoitov@marvell.com, dbogdanov@marvell.com,
pbelous@marvell.com, ndanilov@marvell.com
Subject: Re: [PATCH net-next] net: atlantic: add set_power to fw_ops for atl2 to fix wol
Date: Wed, 02 Jul 2025 02:40:25 +0000 [thread overview]
Message-ID: <175142402549.183540.7984616141525583099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250629051535.5172-1-work.eric@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 28 Jun 2025 22:15:28 -0700 you wrote:
> Aquantia AQC113(C) using ATL2FW doesn't properly prepare the NIC for
> enabling wake-on-lan. The FW operation `set_power` was only implemented
> for `hw_atl` and not `hw_atl2`. Implement the `set_power` functionality
> for `hw_atl2`.
>
> Tested with both AQC113 and AQC113C devices. Confirmed you can shutdown
> the system and wake from S5 using magic packets. NIC was previously
> powered off when entering S5. If the NIC was configured for WOL by the
> Windows driver, loading the atlantic driver would disable WOL.
>
> [...]
Here is the summary with links:
- [net-next] net: atlantic: add set_power to fw_ops for atl2 to fix wol
https://git.kernel.org/netdev/net-next/c/fad9cf216597
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:[~2025-07-02 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 5:15 [PATCH net-next] net: atlantic: add set_power to fw_ops for atl2 to fix wol Eric Work
2025-06-30 7:41 ` [EXTERNAL] " Igor Russkikh
2025-07-02 2:40 ` 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=175142402549.183540.7984616141525583099.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dbogdanov@marvell.com \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=mstarovoitov@marvell.com \
--cc=ndanilov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pbelous@marvell.com \
--cc=work.eric@gmail.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.