From: patchwork-bot+netdevbpf@kernel.org
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, linux@armlinux.org.uk, andrew@lunn.ch,
hkallweit1@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH net 0/2] net: stmmac: fix WoL issue
Date: Tue, 07 Sep 2021 13:10:06 +0000 [thread overview]
Message-ID: <163102020644.3494.2552562162347505160.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210907105647.16068-1-qiangqing.zhang@nxp.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 7 Sep 2021 18:56:45 +0800 you wrote:
> This patch set fixes stmmac not working after system resume back with WoL
> active. Thanks a lot for Russell King keeps looking into this issue.
>
> Joakim Zhang (1):
> net: stmmac: fix MAC not working when system resume back with WoL
> active
>
> [...]
Here is the summary with links:
- [net,1/2] net: phylink: add suspend/resume support
https://git.kernel.org/netdev/net/c/f97493657c63
- [net,2/2] net: stmmac: fix MAC not working when system resume back with WoL active
https://git.kernel.org/netdev/net/c/90702dcd19c0
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:[~2021-09-07 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 10:56 [PATCH net 0/2] net: stmmac: fix WoL issue Joakim Zhang
2021-09-07 10:56 ` [PATCH net 1/2] net: phylink: add suspend/resume support Joakim Zhang
2021-09-07 10:56 ` [PATCH net 2/2] net: stmmac: fix MAC not working when system resume back with WoL active Joakim Zhang
2021-09-07 13: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=163102020644.3494.2552562162347505160.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=qiangqing.zhang@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 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.