From: Clark Wang <xiaoning.wang@nxp.com>
To: linux@armlinux.org.uk, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com, andrew@lunn.ch,
hkallweit1@gmail.com
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/2] fix mac not working after system resumed with WoL enabled
Date: Wed, 21 Dec 2022 16:01:42 +0800 [thread overview]
Message-ID: <20221221080144.2549125-1-xiaoning.wang@nxp.com> (raw)
Hi,
The issue description is in the commit message.
This patchset is the second version following discussions with Russell.
But the name of each patch has changed, so V2 is not marked in each patch.
Thanks.
Clark Wang (2):
net: phylink: add a function to resume phy alone to fix resume issue
with WoL enabled
net: stmmac: resume phy separately before calling stmmac_hw_setup()
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 16 +++++++-------
drivers/net/phy/phylink.c | 21 ++++++++++++++++++-
include/linux/phylink.h | 1 +
3 files changed, 28 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-21 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 8:01 Clark Wang [this message]
2022-12-21 8:01 ` [PATCH 1/2] net: phylink: add a function to resume phy alone to fix resume issue " Clark Wang
2022-12-22 20:32 ` Piotr Raczynski
2023-01-03 9:46 ` Russell King (Oracle)
2022-12-21 8:01 ` [PATCH 2/2] net: stmmac: resume phy separately before calling stmmac_hw_setup() Clark Wang
2022-12-22 20:04 ` Piotr Raczynski
2022-12-22 19:56 ` [PATCH V2 0/2] fix mac not working after system resumed with WoL enabled Piotr Raczynski
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=20221221080144.2549125-1-xiaoning.wang@nxp.com \
--to=xiaoning.wang@nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.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
all inboxes | Powered by JetHome®