From: patchwork-bot+netdevbpf@kernel•org
To: Ismail@ci•codeaurora.org,
Mohammad Athari <mohammad.athari.ismail@intel•com>
Cc: peppe.cavallaro@st•com, alexandre.torgue@st•com,
joabreu@synopsys•com, davem@davemloft•net, kuba@kernel•org,
mcoquelin.stm32@gmail•com, boon.leong.ong@intel•com,
weifeng.voon@intel•com, vee.khee.wong@intel•com,
tee.min.tan@intel•com, netdev@vger•kernel.org,
linux-stm32@st-md-mailman•stormreply.com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH net] net: stmmac: cleared __FPE_REMOVING bit in stmmac_fpe_start_wq()
Date: Fri, 30 Apr 2021 21:50:09 +0000 [thread overview]
Message-ID: <161981940922.13877.7364921069521536310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210429230104.16977-1-mohammad.athari.ismail@intel.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 30 Apr 2021 07:01:04 +0800 you wrote:
> From: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel•com>
>
> An issue found when network interface is down and up again, FPE handshake
> fails to trigger. This is due to __FPE_REMOVING bit remains being set in
> stmmac_fpe_stop_wq() but not cleared in stmmac_fpe_start_wq(). This
> cause FPE workqueue task, stmmac_fpe_lp_task() not able to be executed.
>
> [...]
Here is the summary with links:
- [net] net: stmmac: cleared __FPE_REMOVING bit in stmmac_fpe_start_wq()
https://git.kernel.org/netdev/net/c/db7c691d7f4d
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-04-30 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 23:01 [PATCH net] net: stmmac: cleared __FPE_REMOVING bit in stmmac_fpe_start_wq() mohammad.athari.ismail
2021-04-30 21:50 ` 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=161981940922.13877.7364921069521536310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=Ismail@ci$(echo .)codeaurora.org \
--cc=alexandre.torgue@st$(echo .)com \
--cc=boon.leong.ong@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=joabreu@synopsys$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=mohammad.athari.ismail@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peppe.cavallaro@st$(echo .)com \
--cc=tee.min.tan@intel$(echo .)com \
--cc=vee.khee.wong@intel$(echo .)com \
--cc=weifeng.voon@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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