From: patchwork-bot+netdevbpf@kernel.org
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew@lunn.ch, d-tatianin@yandex-team.ru,
marco@mebeim.net, mailhol.vincent@wanadoo.fr,
korotkov.maxim.s@gmail.com, gal@nvidia.com, jiri@resnulli.us,
kuniyu@amazon.com, simon.horman@corigine.com,
florian.fainelli@broadcom.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] ethtool: ioctl: account for sopass diff in set_wol
Date: Wed, 14 Jun 2023 05:10:29 +0000 [thread overview]
Message-ID: <168671942914.26522.8914520829149345552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1686605822-34544-1-git-send-email-justin.chen@broadcom.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Jun 2023 14:37:00 -0700 you wrote:
> sopass won't be set if wolopt doesn't change. This means the following
> will fail to set the correct sopass.
> ethtool -s eth0 wol s sopass 11:22:33:44:55:66
> ethtool -s eth0 wol s sopass 22:44:55:66:77:88
>
> Make sure we call into the driver layer set_wol if sopass is different.
>
> [...]
Here is the summary with links:
- [net-next] ethtool: ioctl: account for sopass diff in set_wol
https://git.kernel.org/netdev/net-next/c/2bddad9ec65a
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-06-14 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 21:37 [PATCH net-next] ethtool: ioctl: account for sopass diff in set_wol Justin Chen
2023-06-12 22:28 ` Andrew Lunn
2023-06-12 23:00 ` Justin Chen
2023-06-14 5:10 ` 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=168671942914.26522.8914520829149345552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=d-tatianin@yandex-team.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=gal@nvidia.com \
--cc=jiri@resnulli.us \
--cc=justin.chen@broadcom.com \
--cc=korotkov.maxim.s@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=marco@mebeim.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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