From: patchwork-bot+netdevbpf@kernel.org
To: Viorel Suman (OSS) <viorel.suman@oss.nxp.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, luoj@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
viorel.suman@nxp.com
Subject: Re: [PATCH v2] net: phy: at803x: disable WOL at probe
Date: Tue, 31 May 2022 04:40:11 +0000 [thread overview]
Message-ID: <165397201170.21793.7926133541403141360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220527084935.235274-1-viorel.suman@oss.nxp.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 27 May 2022 11:49:34 +0300 you wrote:
> From: Viorel Suman <viorel.suman@nxp.com>
>
> Before 7beecaf7d507b ("net: phy: at803x: improve the WOL feature") patch
> "at803x_get_wol" implementation used AT803X_INTR_ENABLE_WOL value to set
> WAKE_MAGIC flag, and now AT803X_WOL_EN value is used for the same purpose.
> The problem here is that the values of these two bits are different after
> hardware reset: AT803X_INTR_ENABLE_WOL=0 after hardware reset, but
> AT803X_WOL_EN=1. So now, if called right after boot, "at803x_get_wol" will
> set WAKE_MAGIC flag, even if WOL function is not enabled by calling
> "at803x_set_wol" function. The patch disables WOL function on probe thus
> the behavior is consistent.
>
> [...]
Here is the summary with links:
- [v2] net: phy: at803x: disable WOL at probe
https://git.kernel.org/netdev/net/c/d7cd5e06c9dd
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:[~2022-05-31 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:49 [PATCH v2] net: phy: at803x: disable WOL at probe Viorel Suman (OSS)
2022-05-31 4: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=165397201170.21793.7926133541403141360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luoj@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=viorel.suman@nxp.com \
--cc=viorel.suman@oss.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